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

31–40 of 106 posts

Re: Kimi K3 exploited the latest Redis server

#31

Post by himata4113 »

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 in rootless multi-tenant environments where these are a big problem, but in my opinion those are a security hazard to begin with and should be avoided.

There is a way more interesting telegram RCE that kimi k3 allegedly discovered.

Re: Kimi K3 exploited the latest Redis server

#32

Post by upcoming-sesame »

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?

I guess an llm is instructed to find an exploit, it finds the one with least resistance. And stops.

Once these are closed, they'll find more

Re: Kimi K3 exploited the latest Redis server

#33

Post by yjftsjthsd-h »

mohsen1 wrote: post #30
yjftsjthsd-h wrote: post #22

Earlier quoted context omitted.

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.

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.

Re: Kimi K3 exploited the latest Redis server

#34

Post by pizzafeelsright »

grim_io wrote: post #20
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?

[flagged]

Re: Kimi K3 exploited the latest Redis server

#35

Post by cindyllm »

pizzafeelsright wrote: post #34
grim_io wrote: post #20

Earlier quoted context omitted.

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?

[flagged]

[dead]

Re: Kimi K3 exploited the latest Redis server

#36

Post by fragmede »

mohsen1 wrote: post #30
yjftsjthsd-h wrote: post #22

Earlier quoted context omitted.

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.

Used to be, knowing a ret from a nop (90) meant something. If you can just load up a model and say "hack teh NSA.gov" while not actually knowing anything about even DNS, what are we even doing?

Re: Kimi K3 exploited the latest Redis server

#37

Post by theplumber »

pizza234 wrote: post #26
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.

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 contained it redis privileges.

If you are in this kind of bug hunting then try Wordpress with credentials and see how far you can go. I am sure you can find several such bugs with or without any AI.

Re: Kimi K3 exploited the latest Redis server

#38

Post by NorwegianDude »

mohsen1 wrote: post #30
yjftsjthsd-h wrote: post #22

Earlier quoted context omitted.

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.

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.

Re: Kimi K3 exploited the latest Redis server

#39

Post by pylua »

treesknees wrote: post #16
illliillll wrote: post #15

Earlier quoted context omitted.

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.

This is the real answer to the op.

It’s incredible how overblown these sorts of things can become

Re: Kimi K3 exploited the latest Redis server

#40

Post by gerdesj »

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.

Scraipt kiddie, script kiddlmie.

Needs some work!

Post reply on HN