Live data from Hacker News

Kimi K3 exploited the latest Redis server

twitter.com

91–100 of 106 posts

Re: Kimi K3 exploited the latest Redis server

#91

Earlier quoted context omitted.

Open weight, not open source. There is no way to reproduce the model.

you dont need to reproduce it, if you can finetune it. The alignment in these models is really narrow, it doesnt take many finetuning steps to get out of the alignment basin. the alignment is not data centric but done after the fact using RL...

You can write mods for Minecraft too but that doesn’t make Minecraft open source.

Re: Kimi K3 exploited the latest Redis server

#92
post #7

Earlier quoted context omitted.

This is a concern but given its size, it's also going to cost a potential user $500-600k in hardware to self host and run Kimi K3 at any useful speed with full context size. It's not something that just anyone interested in attacking a system can use. The size/cost of hardware is far beyond even something like a self-hosted GLM5.2 Q8 at approx. 850GB GGUF file on disk size, which can run at a slow tok/s rate on a ser…

Why would you caculate 500k? if Kimi is around 1-3tb big, even current DDR5 prices are at 15k.

To run it "at useful speed"

Re: Kimi K3 exploited the latest Redis server

#93
post #30

Earlier quoted context omitted.

Do you think any programmer really understands how their program works end-to-end? At some abstraction layer, we're all clueless. There are many layers between what you type into the text editor and the actual CPU ticks that make your program work. I bet nobody fully understands the whole stack. Now that that text editor accepts English, we're all calling each other names, etc.

I didn't say that Real Hackers™ understood every single thing perfectly from editor to electrons. You've made up a strawman and then beaten it.

I can’t believe the nerve of that guy to straw man your no true Scotsman like that

Re: Kimi K3 exploited the latest Redis server

#94

As wild as this sounds, redis should not exposed to the internet and this appears to be an authenticated RCE. This is similar to claiming that a PSQL query grants code execution when its actually a feature. These systems are typically not tested as aggressively against vulnerabilities of that nature since 10 times out of 10 you have to have access to these systems already. Issues like these are only really an issue i…

Yep. For managed postgres our threat model is to assume vm is compromised. It's paid off, just earlier this year there was RCE fix in PG 18.4

Re: Kimi K3 exploited the latest Redis server

#95
post #6

> this is the first llm that is capable and willing to write an exploit An open-source Kimi is going to have real economic impact (and not only because of its forcing function on frontier labs to indefinitely subsidize their models to meet a race-to-the-bottom market price). Because it's also putting sophisticated zero-day-seeking tools in the hands of script kiddies who can develop and run novel exploits against arb…

If the AI tools can easily find exploits, cannot those same tools be used to harden security? In fact the companies have an advantage over script kiddies: access to more expensive models and compute time as well as professional security engineers

Of course, but there is a big asymmetry: For some systems there are a lot more people interested in hacking them, compared to those interested in protecting them.

But i guess it's also a matter of money, because a company could potentially balance that by throwing x times more agents etc. at it.

Re: Kimi K3 exploited the latest Redis server

#96
post #30

Earlier quoted context omitted.

Do you think any programmer really understands how their program works end-to-end? At some abstraction layer, we're all clueless. There are many layers between what you type into the text editor and the actual CPU ticks that make your program work. I bet nobody fully understands the whole stack. Now that that text editor accepts English, we're all calling each other names, etc.

While most don't, there are developers who actually do understand systems from end to end. Most developers are terrible developers, compared to the really good ones.

[deleted]

Re: Kimi K3 exploited the latest Redis server

#97
post #93

Earlier quoted context omitted.

I didn't say that Real Hackers™ understood every single thing perfectly from editor to electrons. You've made up a strawman and then beaten it.

I can’t believe the nerve of that guy to straw man your no true Scotsman like that

That is... also a strawman. There are less skilled bad actors. There are more skilled bad actors. The bottom rung is script kiddies, so named because they just run other people's scripts. They are not Scottish.

Re: Kimi K3 exploited the latest Redis server

#98
post #76

Earlier quoted context omitted.

>There is a way more interesting telegram RCE that kimi k3 allegedly discovered. Telegram server or client? The client is open source, so I expect any reasonably capable model to find things there sooner or later. But the sever is closed source. Finding an RCE there would be wild for such a model, since it would have to solve a whole bunch of adjacent problems instead of just digesting tons of code.

I mean having the client source code can show you a vast number of the API's and their fields which allows you to fuzz the server quite a bit more easily.

Maybe. The RCE was on the Telegram Desktop client though.

Re: Kimi K3 exploited the latest Redis server

#99
post #86

Earlier quoted context omitted.

Why would they need to selfhost? They can run it via API ala openrouter or runware or whatever. Or on runpod with rented gpus or inference.

Outsourced LLMs are usually censored. It's presumed if you want uncensored, you have to run it yourself.

Jailbreaks exist and work...

Re: Kimi K3 exploited the latest Redis server

#100

Earlier quoted context omitted.

No, that’s a flawed analogy, because this is an RCE. It's (like) having credentials for a network service, then exploiting that service to execute arbitrary code on the Windows host (of course the blast radius depends on the underlying permissions). Access to Redis is not access to the underlying server.

You are right but running Redis or any database without a firewall in 2026 is already a quite bad posture. Now with credentials as well that’s pretty much as bad as it can be. >> Access to Redis is not access to the underlying server. Then you should make sure you run it with the right privilege and consider it potential rogue so when it gets hacked you don’t have to worry about the blast radius because it’s containe…

A firewall can reduce who gets an opportunity to exploit this, but does not make an authenticated RCE irrelevant. This access pattern is perfectly legitimate for hosted Redis services, for example.
Post reply on HN