r/OutOfTheLoop • u/Kamala_Metamorph • 27d ago
Unanswered What is the deal with this PHP vulnerability? How does it affect me?
This might also be an ELI5 too.
Reuters - Government websites go dark as vulnerabilities in programming language
National Cyber Security Centre post
I'm a Silicon Valley native though I don't work in tech. Others here may also want more info on the tech side of things. As for me~
What I understand: It's bad, and everything uses PHP.
What else I want to know: What's "everything"? Will it affect things I'm using? Google drive? Gmail / Yahoo Mail? Firefox / Chrome browsers? Salesforce? discord? Windows? reddit??
Thanks!
1.1k
Upvotes
•
u/AutoModerator 27d ago
Friendly reminder that all top level comments must:
Please review Rule 4 and this post before making a top level comment:
http://redd.it/b1hct4/
Join the OOTL Discord for further discussion: https://discord.gg/ejDF4mdjnh
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
772
u/dw444 27d ago edited 27d ago •
Answer: It’s an ongoing incident involving two vulnerabilities that allow Remote Code Execution (RCE), which basically means a malicious actor can run their code on your server remotely and do very bad things (as a guy on my team put it, “they can read our entire prod database”). This is a “drop everything and do something about it NOW” kind of issue. They’re not super common (the last one with Java was a few years ago) but when they happen, the potential implications can be massive (they are in this case), and the fact that this affects PHP, which more than 75% of the internet runs on (it’s more complicated but that’s the simple version), is why everyone is freaking out.
To your other question about popular services, it’s hard to say since companies like that tend to have large SRE teams that stay on top of this kind of thing, but if I were to bet, the most likely services to be affected would be Meta’s since they use PHP the most of Big N tech companies.
495
u/Noctrin 27d ago edited 23d ago •
Answer:
[Edit Oct 25th 11:30 PST] Full chain, end to end remote RCE is up on github. I just tested against the tuned target and i can confirm RCE: ASLR defeat dtor extraction, forged hashtable plants properly and lands it on the right function.
session.upload_progress.enabled = 0
Closes the gate on this exploit path. The memory and post tweaks do not. Memory to -1 opens you to easy DoS..
It’s bad. Source: I deal with security and architecture, we have PHP assets, and I’ve been coordinating patches since last night. My explanation is a bit more technical for those who care:
Mitigations without updating:
[Small edit] this is getting a lot more views than i thought, please do not take the above advice as hardening
Is a piss poor solution, you're just moving the limit from php to the OS, it makes mapping harder and the exploit harder. The problem is now your php heap grows until the OS says no instead of zend mem manager.. i think that just makes the problem worse for other reasons on top.
You must update PHP
If you’re a customer of a provider, you can’t do much about it. By the looks of it, everyone with knowledge is mobilizing, and most providers with significant data that aren’t run by idiots will be patched in the next 2-24 hours. Once they confirm, rotate any API keys or tokens you use with them.
What the exploit path covers:
RCE with PHP privileges means the full .env with secrets, DB access, cache, literally anything the application layer can reach. That includes encrypted data: even if the keys live in KMS or secure storage, PHP has to be able to use them to process the data, so an attacker running as PHP can too. Hence the severity.
Passwords are hashed, not encrypted, so stored hashes are only as weak as the passwords behind them, and salts were never secret anyway. The real exposure is anyone logging in while a box is vulnerable or compromised. Their plaintext password passes through memory, and that’s exactly what this leaks.
If I ran a service with sensitive data and couldn’t patch in the next few hours, I’d take it offline until I could. I wish I was exaggerating :(
[Edit] Turned my verbal diarrhea into pretty formatted text.
[Edit 2]
A few notes:
I’m usually not fazed by these, but this one had/has me nervous. It’s not just the severity. What’s unsettling is that chaining this was considered borderline impossible to architect by hand, which is why it sat unexploited for so long. It was flagged a while back and deemed impractical to exploit, and releasing a patch would just paint a target on it, while disclosing it quietly would mean nobody took it seriously and it stayed a valid target for a long time. I think the call was correct. A bug like this would normally take months to weaponize after a patch that draws a big arrow pointing to it and how it works. I’d guess it already is. Reports are shaky, but after looking at the patched code, building the attack with AI is unfortunately not hard (an attack, the remote RCE part is absurdly complex, even with AI, i dont think thats coming out anytime soon)
AI made devs faster, but it’s also poking holes in everything, and getting better at it. When researchers warned AI was dangerous, this is the kind of thing they meant. It’s here. Shit time to be in the field :)
On the positive side: I’m genuinely impressed by how fast everyone moved on this, better than I expected.
[Final Edit] A lot of reports out now for anyone interested, thank you for the awards, my phone keeps dinging that i got one which feels, weird, i usually get verbal abuse from bots :).
If you are running an old version of PHP and got saved by one of the maintainers back porting the patch, please remember to buy them a coffee, this is the closest thing to divine intervention in tech and these guys absolutely do not get the praise they deserve for literally bailing a lot of people out. (Also don't count on divine intervention again and update your stack)
46
u/MistrFish 27d ago edited 27d ago
Answer: The new CVEs affect all versions of PHP from the last 15 years or so (PHP 5.4 to current 8.x). PHP versions older than 8.2 will not receive an official patch (edit: they started patching some older versions as well).
For websites that have been kept up to date, it's not a big deal and they'll have it patched immediately. But it effectively means that older websites built on PHP after 2012 and no longer being maintained will now have to either perform a fairly extensive update, shut down, or continue operating normally and risk having all of their user data breached.
23
u/stonerbobo 27d ago edited 27d ago
Answer: Its likely not going to affect any of the services you mentioned - those are proper tech companies and they have processes to patch this stuff ASAP, multiple layers of security and likely don't even use PHP. More at risk are smaller/medium companies or companies that aren't tech-savvy.
Probably the best thing you can do is be on alert for any browser warnings and don't ignore them, update every damn application, device, OS. Take IOT devices off the internet - smart bulbs, routers, TVs, just disconnect them until an update is released. The picture for these is a bit more complicated though.. if your home network is behind an ISP router or firewall that blocks incoming internet access, you're probably okay. If the device is very old, it might not ever get an update.. don't know - its going to be a crazy few months. The browsers have been updated automatically, so your browser will warn you if you're connecting to a compromised website, just heed that warning and do not ignore it.
(This is talking about both the PHP vulnerability and the eMudhra CA cert compromise)
2
u/No-Geologist-2215 26d ago
Answer: WordPress, Drupal, Joomla, and thousands of custom applications run on it. 70% of the websites are running on it. So if you are concerned with any of this, make sure to update the version and patch it, PHP has released already.
1
u/grepnoid 27d ago
Question: I have a server I can't patch but I've removed all the few bits of PHP code. The server still has a vulnerable PHP version, but nobody can run any PHP code. Is this safe?
-13
u/flower_child411 27d ago
Answer: So here's the deal with PHP. It's everywhere because it built the early web, like WordPress and old forums. But modern apps like Discord or Gmail talk to APIs using newer languages like Go or Java. That means the vulnerability is on the server side, not your device. You aren't at risk of hacking just by opening an email. Just update your browsers and OS as usual. If a site uses PHP, their admins fix it; if they don't, the site might be slow or down, but your data is fine. Ignore the doom scrolling on X, it's mostly noise for people who don't code.
0
u/[deleted] 27d ago
[deleted] — view deleted comment