I've seen some posts about this, but I'm not sure they make the news clear enough: if you work with PHP, you need to be ready tomorrow between 14:00 and 14:30 UTC for the arrival of another critical security update
@falken I would always encourage people to patch rather than relying on configuration. But your setup, your priorities
@jalefkowit I am skeptical of this, after the last one was revealed to take a serious amount of sustained, targeted effort to exploit.
But devoid of any actual info (and rightly so, I appreciate that the PHP folks take this seriously), I guess I have to care regardless.
@hypolite @jalefkowit Cheap, but not free. The last one was demonstrated by https://stealmybitcoin.com/ to take hours by many attackers against a single target with heavy LLM assistance. AFAIK the person who successfully cracked the server didn’t say how much they spent on the LLMs.
@hypolite I think I mostly agree with that. I would hope you’d lock down your web server, but at the very least they could pilfer your DB credentials.
Not sure what the ramifications of this new vulnerability are.
@jalefkowit oh wow again? Thank you for the heads up!
@jalefkowit It's out and no description of the issue or mitigations. 🤬
@jalefkowit For anyone wondering, I've found it's basically new FPM exploits: GHSA-jm4m-qfqx-967m, GHSA-qc49-hpvq-g2w6, GHSA-3mg3-cr28-46gc. A privilege escalation if you're already able to RCE. RCE as php-fpm user if connection re-use is enabled(it isn't by default). An XSS injection through Basic Auth(if sent through php-fpm for processing) or more complicated vector.
So mostly another nothing burger.
@jalefkowit > The issues rated CRITICAL require either non-default configuration or uncommon setups.
So probably fine.