hello, btw what's Php? and why is everyone on IT is panicking about it?
So! The PHP exploit is an area of software that is like... a few doors adjacent to what I do. Which is to say I don't, and haven't, worked directly with PHP. But I've got a solid enough grasp of the ecosystem to in broad strokes understand the issue. (If you ARE a PHP expert, random person reading this, please forgive me if I muddy a few specific details.)
Analogy because I like analogies: You walk into a bank. Within the bank, there is a ton of sensitive, critical, important information about all the people with accounts there, as well as the account information. This sensitive information is not just lying around of course. There is in fact a clearly established infrastructure and protocol within a bank, and the only information you should be allowed to access is your own.
You go up to the teller. You prove your identity. You're now allowed--through the teller--to request information, but only information about your own account. You're beholden to the back-and-forth the teller is willing to have with you.
And websites, like banks, own a lot of information. And while the bank infrastructure is built with physical barriers, bulletproof glass, and tellers who are trained on a very specific protocol they will operate in order to give you only your allowed information, all of that in a website is--for 70% of websites--built in PHP.
Attackers would love to get access to everyone's banking information. A bank teller operating correctly would never just give up that information though. Unless the attacker can exploit a flaw in how the teller is built, in order to access that information anyway.
Two PHP exploits were recently just found via AI auditing. These exploits have technically existed for a very very long time. But the way to use the exploit, for both of them, was so highly improbably specific that--either--it was deemed safer to never address the problem (to keep attackers from learning about it via the fix), or maybe just never truly considered.
A huge risk, as AI becomes far more prominent, is that AI is really good at doing and trying everything at a rate humans cannot. I think we're going to be seeing a lot more "it would be so highly improbable for a human actor to come across the extremely specific circumstances to exploit this issue, but AI found it" security problems.
Anway, the two exploits are both some flavor of "make a fatal issue with a request occur at an extremely specifically timed moment" that leaves some task half-completed and leaves vulnerable memory accessible/uncleared. Between the two exploits, two prominent issues exist
2. RCE - remote code execution
The first one, on the bank teller analogy, is like if you could make the teller fail to put away the previous customer's sensitive documents by the time it's your turn. So even though you never had the credentials to know about that other person's information, it was never cleared out of your sight so you get to just look at it.
The second one is the golden child of vulnerability exploits. It's like if you could just vault the counter at the bank, say "I'm allowed to be here", pick up a badge that says "I'm the bank manager", and then you order everyone to give you all the information about every single bank customer, and they give you what you ask for because you're the bank manager...!!!!!
These KINDS of exploits aren't new or unique. But the impact to PHP makes this extremely hard-hitting, because ~70% of websites are built on PHP, and this problem only goes away if the current, active, maintainers of those websites upgrade their PHP version to the latest, which patches the issues. (There is no way to automate this. There is no "just push the PHP fix to every website automatically." It doesn't work in that direction. The owners of every website have to actively do it.)
But also, PHP only patches the current, supported versions of PHP. There is a mountain of ancient websites that are on ancient versions, either because no one has maintained that website in years, or because the burden of interconnected dependencies would mean updating PHP would break something else.
So. That random forum you went to in 2010 that hasn't been maintained in years, is on a crazy out of date version of PHP, and is still hosted? Maybe no one's fixing that, probably. Attackers can walk in and say "I'm the bank manager" and take your username and password.
Also, because AI operates so quickly and in such enormous scale, attackers utilizing AI can very easily bullet spray websites with this kind of attack. (Not brand new to AI, but AI makes it way way way easier.) The only safe websites are the ones who were able to jump instantly enough to update their version of PHP to now be protected.
But the massive glut of outdated, unmaintained, un-updateable websites out there (the 70% of them using PHP) are just indefinitely exploitable, until someone takes them offline or does the PHP update.