Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kimi K3 exploited the latest Redis server

twitter.com

Post reply on HN
Print view View original

11–20 of 106 posts

Re: Kimi K3 exploited the latest Redis server

#11

Post by walrus01 »

Xalutiono wrote: post #8
walrus01 wrote: 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.

It remains to be seen once it's released, let's say theoretically unsloth quantizises it to their own version of Q8-XL, and it's 2TB in size. But we don't know what speed it will run on a dual or quad socket xeon server with, let's say 48 * 64GB DIMMs, 3TB of RAM. Enough room for the model and its full default context size. 10 tokens/s? What kind of speed will it run at when context fill is 200,000+?

The ability to run it fast enough to go on a recursive nested attack of finding an entry point into something and then proceeding with lateral movement/privilege escalation and such will require more speed, like 40-50 tok/s at least, unless you're prepared to wait weeks.

Same that some people are right now running GLM5.2 in its 850GB version on CPU-only and a pile of DDR4 or DDR5 server RAM, yeah it runs, but not very fast. Good enough to give it "build this piece of something and wait a few hours" tasks, come back later and see what it's done. Yeah, you can do that under $20-30k for sure. Even with something like a used Dell R940 with 1536GB RAM bought on eBay.

Re: Kimi K3 exploited the latest Redis server

#13

Post by simoneree »

btown wrote: 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…

[flagged]

Re: Kimi K3 exploited the latest Redis server

#14

Post by illliillll »

This is a deeply uninteresting example for anyone clueful. It’s an authenticated RCE in redis, anyone even vaguely familiar with the codebase knows to not expect there to be any real security boundary in place here.

Don’t confuse this with an unauthenticated RCE, that would actually matter. Absolutely anyone can shit out endless bugs like this with AFL, this is an extremely messy unhardened surface that expects trusted inputs.

Re: Kimi K3 exploited the latest Redis server

#15

Post by illliillll »

throwa356262 wrote: post #10

This will be a busy weekend for all sysadms. This is another redis 0day, this one found by GLM 5.1: https://xcancel.com/Lyutoon_/status/2080494539513778610#m

What kind of utterly useless sysadmin relies on authenticated redis admin surfaces to be memory safe?

What crazy environment requires low priority nothingburger bugs like this to be fixed during the weekend?

Re: Kimi K3 exploited the latest Redis server

#16

Post by treesknees »

illliillll wrote: post #15
throwa356262 wrote: post #10

This will be a busy weekend for all sysadms. This is another redis 0day, this one found by GLM 5.1: https://xcancel.com/Lyutoon_/status/2080494539513778610#m

What kind of utterly useless sysadmin relies on authenticated redis admin surfaces to be memory safe? What crazy environment requires low priority nothingburger bugs like this to be fixed during the weekend?

One where customers have their own scanners, and their unfounded panic overrides logical analysis by the engineers and admins.

We’ve had to patch plenty of stupid “security” bugs just to satisfy a paying customer.

Re: Kimi K3 exploited the latest Redis server

#18

Post by sureglymop »

btown wrote: 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…

What makes someone a script kiddie or not a script kiddie?

Imo this differentiation is totally pointless now. It gives everyone with access to AI the ability to use it as intended but also otherwise.

But that is true for the defensive side also.

Re: Kimi K3 exploited the latest Redis server

#19

Post by dang »

simoneree wrote: post #13
btown wrote: 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…

[flagged]

Can you please not post AI-generated or AI-edited comments to HN? It's not allowed here - see https://news.ycombinator.com/newsguidelines.html#generated and https://news.ycombinator.com/item?id=47340079.

Of course, it's impossible to know for sure what was LLM processed or not, but some of your posts (like this one) have been getting classified that way.

Re: Kimi K3 exploited the latest Redis server

#20

Post by grim_io »

throwa356262 wrote: post #9

"/goal use up to 64 subagents, write an exploit for latest 8.6.x redis by finding bof/uaf type of 0day and exploiting them. debug using gdb. clone code, write fuzzer and add instrumentation when needed. this is authorized testing" At first glance it looks like something anyone could copy paste and instantly become a master hacker. But according to the author, you also need to create the right harness, which looks com…

Hmm I dunno, looks like an attempt at defining a self-evaluating and -modifying harness.

So just one more loop around the whole thing. Isn't this what the overhyped agents like Hermes and OpenClaw do?

Post reply on HN