logoalt Hacker News

grey-area • yesterday at 10:31 PM • 4 replies • view on HN

Seems like everyone here has an exploit but they're all busy washing their hair, or thinking of the children, or making huge amounts selling their exploit on the darknet instead.

Given there are public patches and explanations of the issue, isn't it a little late to try to keep this under wraps?

Over a day or two we'll see whether people have an exploit - if more than a few people do, someone will claim this $1k soon. Out of curiosity, what do you plan to do with your exploit that you're holding back?


Replies

Nition • yesterday at 11:22 PM

Unfortunately I left all my easy PHP exploits together with my pre-2023 writing that Pangram flags as 100% AI in Canada with my long-distance girlfriend.

➕ show 1 reply
seanhunter • yesterday at 11:40 PM

I have discoverd a truly marvelous RCE which this margin is too narrow to contain.

➕ show 1 reply
TZubiri • today at 2:23 AM

It's done, anyone still talking about this is in the business of monetizing trending keywords (or crime), not in the business of cyberdefense.

Anyone that's thinking about defending basically stopped thinking professionally about this on Thursday midday when the PHP update was released and the patch was applied. Maybe on Friday we learned that there were no confirmed exploits or even theoretical exploits, so we discarded the marginal possibility of our servers being exploited stealthily and having a dormant attacker in our perimeter (it was a buffer overflow attack after all, very hard to execute).

So it's out of mind for us, it's almost saturday, the only reason to think about this anymore is to grift or to think about the social contagion angle. To many of us it was a random tuesday, business as usual, but some people are still thinking this was a somehow special event? My guess is that it was the fact that there was an embargo break and it caused some issues in that 12 hour period between the leak and the patch, but it was a nothingburger, now it just needs to die, at least after it makes its round through the content-creators whose 9 to 5 is looking at trend charts and monetizing views.

DetroitThrow • yesterday at 10:48 PM

The only reason Php2shell wasn't as bad as it could've been was because basically no malicious actors had exploits that were useful in time.

Whoever broke the embargo is a moron and it could have resulted in much more damage than was done.

➕ show 2 replies