I am very curious to hear why you thought it was overblown.
There was also that other guy who posted "steal my bitcoin" on a vulnerable PHP server with the private keys to prove it was overblown, and got his bitcoin stolen within a day.
[–] jerf 14 hours ago
[–] NitpickLawyer 14 hours ago
[–] jerf 12 hours ago
[–] 0x457 7 hours ago
Doesn't mean that there isn't another exploit chain that can be used though. Challenge also had 4 workers total, so pining one worker wasn't that hard.
[–] kylestanfield 11 hours ago
[–] cowlevel 14 hours ago
I don't see what was confusing about the initial 24 hours. GP was correct, the description of the bug made it clear it was a very high risk.
[–] beepbooptheory 13 hours ago
[–] cowlevel 13 hours ago
[–] jstanley 14 hours ago
It could be overblown if it's not true. The amount of time it took for anyone to claim the Bitcoin from the supposedly-vulnerable PHP site convinced a lot of people that the vulnerability was not as bad as claimed.
[–] jooops1 8 hours ago
[–] tkz1312 14 hours ago
[–] lifeisloving 14 hours ago
This was not a scary vuln at all.
[–] literalAardvark 12 hours ago
It's a horrible vuln and I don't understand what's with all the flat infosec society coming out of the woodwork.
The challenge server had vibe coded infra that made it hard or impossible to hack, but it was a configuration that can't be used in production and no one uses ( it was deployed as a PHP static content server instead of a dynamic site generator )
[–] pixl97 10 hours ago
Ha, while most of these are probably humans that are just being driven mad by AI, I wonder how long before we get AI driven botnets that try to under play any security vulns to give them more time to take over and collect assets for themselves?
[–] 9dev 7 hours ago
[–] Urd- 13 hours ago
[–] lifeisloving 12 hours ago
This is a seperate chained exploit itself, seemingly executed by a nation stae. There are thousands of exploits infiltrating web servers around the world daily, and they arent php2shell.
You only care about this because it falls into a weird viral narrative about "AI saftey".
[–] literalAardvark 11 hours ago
Chained just means they used php2shell to run a local privilege escalation.
[–] lifeisloving 11 hours ago
[–] cowlevel 14 hours ago
And would you stake your bitcoin on it?
[–] devin 11 hours ago
[–] lifeisloving 10 hours ago
[–] jrflo 14 hours ago
[–] swat535 9 hours ago
[–] 1718627440 14 hours ago
Not having made the claim (took down my website too), but because PHP is not connected directly to the network. While you cannot prevent PHP from being overtaken from inside the PHP program, you can prevent PHP being executed on malicious data by configuring the webserver. It's overblown in the sense that it would be even more serious if the same happened in the webserver itself.
[–] cowlevel 14 hours ago
[–] 1718627440 13 hours ago
[–] cowlevel 12 hours ago
[–] kalleboo 2 hours ago
[–] 1718627440 12 hours ago
[–] cowlevel 12 hours ago
> you can prevent PHP being executed on malicious data by configuring the webserver.
[–] jstanley 12 hours ago
[–] 1718627440 11 hours ago
[–] lifeisloving 14 hours ago
The whole thing was basically a psyop, whether intential or not idk but Califs research was funded in part by OpenAI so there's that.
[–] robby_w_g 13 hours ago
It was OpenAI's marketing that hyped up the vulnerability to the point that guys on my hockey team saw it in the news and were asking about it. There doesn't need to be mainstream articles about it, these kinds of vulnerabilities happen every year. Just patch and move on.
[–] literalAardvark 11 hours ago
Random bloggers jumped on it and said dumb blogger things. That is all.
This is one of the worst vulns ever and the security response from the people who actually secure things for a living was entirely warranted regardless of whether some blogger thought it was the AI apocalypse or not.
19 hours: https://stealmybitcoin.com/
Part of the confusion is that the initial PR for the release made it sound like there was a ready-to-go exploit that was just push button, get shell on any PHP server in the world. That turned out not to be the case, as evidenced by the fact that the number was 19 hours and not 19 minutes.
But the fact that it was 19 hours and not "never" also does provide a data point that everything that was vulnerable really was vulnerable, it just may not have been quite as vulnerable as it was initially presented. Still plenty vulnerable, of course.
My point here being that the initial 24 hours were very confusing and I think it's worth remembering that and giving people grace for it. Even now, I've heard rumors of an exploit that does work on all boxes without making changes for a specific target but I'm not actually sure whether that exists or not. (Any further info welcome.)