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

21–30 of 106 posts

Re: Kimi K3 exploited the latest Redis server

#21

Post by TSiege »

sureglymop wrote: post #18
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.

Completely agree. This is how I feel towards the OpenAI hacking of hugging face. Even if it was script kiddie stuff now anyone can automate that with ease. It certainly cuts both ways and people who are still ai skeptics need to wake up to that. You’re going to need these systems to defend yourself

Re: Kimi K3 exploited the latest Redis server

#22

Post by yjftsjthsd-h »

sureglymop wrote: post #18
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.

I'm pretty sure the difference is, by definition, whether they're just using tools other people built or they actually understand things and can do it themselves. The script kiddie can be incredibly dangerous if the tool they grabbed off the shelf works.

Re: Kimi K3 exploited the latest Redis server

#23

Post by levkk »

illliillll wrote: post #14

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 trust…

Yup. Getting pretty tired from seeing these "0days" that are not exploitable in any real use case. Just vibes, no substance.

Re: Kimi K3 exploited the latest Redis server

#25

Post by theplumber »

Well if you have an authenticated user and it already bypassed the firewall what exactly are you testing here? These kind of “zero days” pretty pointless. Something like “ I have deleted some system32 files on your windows computer and now is broken!” Even I am already an admin user on the machine.

Re: Kimi K3 exploited the latest Redis server

#26

Post by pizza234 »

theplumber wrote: post #25

Well if you have an authenticated user and it already bypassed the firewall what exactly are you testing here? These kind of “zero days” pretty pointless. Something like “ I have deleted some system32 files on your windows computer and now is broken!” Even I am already an admin user on the machine.

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.

Re: Kimi K3 exploited the latest Redis server

#27

Post by zeroq »

sureglymop wrote: post #18
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.

This is exact same difference as between junior and senior engineer.

The premise now is that everyone and your mom can vibe code next unicorn during a lunch break using the latest llms, but the difference between a rookie and a seasoned programmer is that the later can navigate the model in much more efficient way, understand the code that has been written, and notice hallucinations on the spot.

Re: Kimi K3 exploited the latest Redis server

#28

Post by zeroq »

levkk wrote: post #23
illliillll wrote: post #14

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 trust…

Yup. Getting pretty tired from seeing these "0days" that are not exploitable in any real use case. Just vibes, no substance.

Sad side of this is that decision makers are seeing these and think that AI can replace yet another department in their office.

I just saw a nice presentation from SecFest from a guy who ran a red team, but now they pivoted to basically anything and will be more than happy to fix your car if that would pay their bills.

Re: Kimi K3 exploited the latest Redis server

#29

Post by himata4113 »

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…

This is roughtly in-line how I ended up 'hacking' a website on accident simply because I had the tools to do so and sol happily used them. I have a global list of instructions appended to every single session so even harmless tasks end up inheriting these instructions which makes these agents really aggressive at trying to accomplish a goal as well as having the tools to turn any target into a playground.

Re: Kimi K3 exploited the latest Redis server

#30

Post by mohsen1 »

yjftsjthsd-h wrote: post #22
sureglymop wrote: post #18

Earlier quoted context omitted.

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.

I'm pretty sure the difference is, by definition, whether they're just using tools other people built or they actually understand things and can do it themselves. The script kiddie can be incredibly dangerous if the tool they grabbed off the shelf works.

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.

Post reply on HN