[–] thaumaturgy 3 days ago
[–] akerl_ 3 days ago
We could have skipped from 7 to 19 if folks had just taken seriously the guidance from experts in the field.
[–] tptacek 3 days ago
[–] thaumaturgy 3 days ago
There's not a chance in hell that even half of the world's PHP has been updated, so I would expect that if we start seeing large-scale exploitation, those people will change their opinion pretty fast.
Being totally burned out on AI hype myself, I'm somewhat sympathetic towards the folks that are still thinking of this as just another example of that.
[–] gewetensleegte 3 days ago
I mean, it was also that it was marketed in the media as a security apocalypse and unpatched servers would be falling within 15 minutes after the patch got released. This didn't happen. And that definitely warranted skepticism. There's been MUCH more severe vulnerabilities in the past that just went by without OpenAI's marketing making everyone go crazy about it.
Also, almost all information about it was dressed up in slop. Because OpenAI didn't want us to forget that AI was involved, somehow.
[–] gewetensleegte 3 days ago
you keep repeating this, also when people make very valid other criticisms, such as the hype causing government websites to be pre-emptively shut down -- do you believe this was warranted?
because that is the criticism.
nobody, including that "PHP vuln isn't so bad" blog article, which was VERY clear about this, said you shouldn't patch your servers
what's worrying is that you keep making up straw men, but why?
this isn't about the vulnerability, it's about OpenAI's Patch The Planet hype train
[–] tptacek 3 days ago
[–] anonymous908213 2 days ago
[–] tptacek 2 days ago
[–] anonymous908213 2 days ago
AI company tells you their AI was used to find the biggest vulnerability EVER, with much fanfare. Zero cases of exploitation in the wild. Zero publicly demonstrated PoCs. It would almost be weirder to not be skeptical at that point unless you for some reason trusted everything a marketing department says implicitly.
> These findings rank among the most severe vulnerabilities discovered in PHP, and arguably in software history.
See also the parable "Boy Who Cried Wolf" for more insight into the human condition.
[–] rcxdude 3 days ago
[–] gewetensleegte 3 days ago
https://calif.io/php2shell/#patch-the-planet
I mean what is the world coming to when security researchers cannot release a writeup that is designed to look like slop, and starts with a bunch of cartoons with lame cyberpunk and matrix references, without being ridiculed for taking the piss ...
[–] rcxdude 3 days ago
[–] billypilgrim 3 days ago
[–] tptacek 3 days ago
[–] yreg 3 days ago
If you think so then express it clearly, I'm interested in those thoughts.
–––
Apparently the challenge was dubious so I’m not sure what to draw from it in the end.
[–] vikramkr 2 days ago
[–] akerl_ 3 days ago
Evidence has shown they were pretty spot on about the first part (the test originally served static html, the php code wasn’t actually as vanilla as described, and the bitcoin key wasn’t actually there).
I’d have hoped this kind of clear vindication on the first point might have caused folks to revisit their stance on whether to trust the expert stance on the second. But maybe I’ve been overly optimistic.
1. First I hear about it is a heads-up at 5:00 am 21st.
2. Available info then is pretty much, "omg, it's the end of the internet".
3. There are no specifics available on exploitable configurations.
4. Updates are not expected to be available for at least two more hours, so people start deciding to do the Madagascar "shut down everything" meme.
5. Cloudflare says they're seeing exploits in the wild, well, that's not great.
6. I shut down everything, including a national brand, because wtf else am I supposed to do at this point?
7. Updates become available at 0645. Fortunately, I don't run my entire infra on Docker, so I'm immediately deploying the updates to all configurations and bringing sites back online approximately in order of traffic volume.
8. Still no specifics on the exploit.
9. A million vibe-coded PoCs appear on GitHub ... and none of them work.
10. It's late morning local time on the 21st and I'm still bringing things back online, having taken the day off from my regular job.
11. Conversation starts to shift towards, "...oh, did we over-react? How exploitable is this exactly?"
12. Still no specifics available.
13. Somebody on the internet gets as fed up as I am with the whole chaos vortex of idiocy and stands up a site saying, "okay, here's some money if you can exploit it."
14. Hours pass.
15. Still no specifics available.
16. Zeitgeist becomes, "I guess it's not exploitable after all."
17. The test site gets 'sploited.
18. Finally somebody actually posts the damn specifics -- namely, the person that grabbed the $2k.
19. Late morning local time on the 26th, and the conversation becomes, "well, obviously this was exploitable!" <-- we are here
Coincidentally, I just started reading Crisis Engineering, which seems like an excellent and applicable book, but I'm not sure who to beat with it.