Remix.run Logo
▲ ishouldnotbutk8 5 hours ago

There was a literal PoC video that started the panic, then multiple writeups. It's not hard (for people who know what they're doing) to exploit the PHP vuln. It's just not one exploit to rule every PHP installation anywhere, since this is a low-level exploit that needs to bypass ASLR, instead of a logic bug - so you need to tweak your exploit for every architecture, system, configuration, etc. And you need to know a fair bit about your target.

The response was overblown, but your dismissive reaction is too far in the other direction.

▲brovonov 5 hours ago | parent | next [-]

It had an anime dancing girl on it, must be serious.

▲zkldi 5 hours ago | parent | prev [-]

Hi, I wrote the blog post and wish I'd just written your exact words instead.

A lot of the lab PoCs still use contrivances (ignoring the ones that are disabling ASLR or just inserting `vulnerable.php` files on the server) that you don't really get in the real world - even the requirement of having to heap groom the same PHP worker repeatedly and sequentially is quite hard to exploit if the website has traffic. (this is why some of the slop PoCs reconfigure apache to have one worker, or pin WORKERS-1 with infinitely long requests).

This is in stark contrast to other, more severe vulns that the internet has seen (and will see in the near future) where there's effectively a blank cheque to fuck anything that is unpatched. This is not a blank cheque. It is still bad.

This doesnt matter though - luck and statistics are not serious security walls. Patch your servers.