Hacker News
points by thaumaturgy 3 days ago | 0 comments
For me (I host a lot of PHP...):

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.

[–] akerl_ 3 days ago
It’s worth noting that while folks were getting busy with 11 and 13, plenty of experts in the field were saying ~“yes, we do have viable exploits here, but we’re not sharing them at this time. This is a big deal.” And that the person who spun up 13 spun up a static html page at first and also misrepresented how vanilla the stack was.

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
I mean, it's clear you have a valid reason to be irritated, but that's not the concern I have here. What's worrying is people applying motivating reasoning to talk themselves (and others) into believing the vulnerability simply isn't a big deal, which is clearly false.
[–] thaumaturgy 3 days ago
Yeah. I'm choosing to believe that those people just over-weighted some previous info and are under-weighting the latest, but I dunno.

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
> 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.

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
> believing the vulnerability simply isn't a big deal, which is clearly false.

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
OpenAI didn't find this vulnerability.
[–] anonymous908213 2 days ago
No, but they were part of the PR blitz. The lack of real-world exploitation + Calif commissioning a fucking webcomic made me skeptical. That's not fucking normal. Given what a huge marketing stunt it turned into, and 1000 vibe coded PoCs that aren't PoCs, it was at least in the realm of possibility that Calif huffed their own vibes too hard. If you want people to take security risks seriously, making them into a media spectacle promoting OpenAI is not the way to do it.
[–] tptacek 2 days ago
What does Calif commissioning a web comic have to do with anything?
[–] anonymous908213 2 days ago
It, along with the press releases and the cutesy domain names registered, shows that this was clearly being played up as a marketing stunt, with planned coordination of such ahead of time. As soon as you begin to use the security incident to communicate a coordinated narrative about how amazing AI is, it's the most given thing in the world that some people will become skeptical of the severity of it and whether it isn't being played up as the most impactful security vulnerability ever found (per the press release claims) solely as part of an attempt to make the AI company sound more impressive.

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.