Top
Best
New

Posted by tuyuri 12 hours ago

PHP 8.2.35(github.com)
Related ongoing thread: Today's PHP security release, and how we're strengthening security - https://news.ycombinator.com/item?id=50182987
967 points | 532 commentspage 7
consocio 9 hours ago|
https://github.com/consocio/php2shell-audit/ GLM 5.3 just wrote it to audit all my php sites. I hope it is useful to you.
dddw 2 hours ago|
Grazi!
DonHopkins 11 hours ago||
Time to restart Apache again!

"I'm not a real programmer. I throw together things until it works then I move on. The real programmers will say 'Yeah it works but you're leaking memory everywhere. Perhaps we should fix that.' I’ll just restart Apache every 10 requests." -Rasmus Lerdorf

bombcar 11 hours ago|
Amusingly enough restarting php after each request seems to block the issue
SoftTalker 10 hours ago||
If true then classic CGI mode should not be vulnerable, but apparently it is.
quotemstr 9 hours ago||
Is it? How? Yes, you can get longjmp to do invalid things, but with an ASLR reset each attempt, can you exploit it?
SoftTalker 8 hours ago||
Not sure how, but from the announcement: Who is at risk: all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.

Maybe just CYA.

quotemstr 8 hours ago||
Also, CGI PHP skips request cleanup on init failure.

I'm 90% sure CGI can't be exploited this way in default configuration with ASLR and 99% sure if PHP is configured with memory_limit=-1

That said, don't be an idiot and switch to CGI instead of patching. I'm like one of three guys running PHP in CGI mode and I'm vaguely satisfied I have the most resistant configuration.

The reason, BTW, I run PHP in CGI mode is so I can (moral equivalent of) suexec to a locked-down sandboxed environment that limits exploit blast radius. I could do the same with fcgi daemon, but the suexec is stateless, and roundcube doesn't need the performance.

In general, anything stateful or long-lived is just one more thing that can go wrong. One reason why the trend of turning everything into a persistent daemon drives me nuts.

febed 8 hours ago||
Any signs of exploits out yet?
alrenai 11 hours ago||
Anyone know if Microsoft updates azure web-app built-in php runtimes fairly quickly in this sort of scenario?
torbengee 11 hours ago||
Looks like the upgrade instructions for PHP 8.3 for Fedora 39 and earlier are not working ... yikes.
dataflow 11 hours ago||
Is PHP 7 essentially going to be dead and unusable for everyone then? Or will it get fixes?
e12e 11 hours ago||
> Given the severity of these vulnerabilities, the PHP security team provided minimal source-backports for PHP 7.4, PHP 8.0, and PHP 8.1 to help people building from source or without access to an LTS vendor.
NiekvdMaas 5 hours ago|||
https://github.com/Niek/php7
guffins 11 hours ago|||
PHP 7 hasn’t received an update since 2022 when it went EOL.

EDIT: looks like there are backports though

Operyl 11 hours ago|||
There are backports already.
kps 11 hours ago||
Debian has a new build of 7.4 at least.
cpncrunch 11 hours ago||
Not out on Ubuntu 20.04 yet, but sometimes they are a little slower. Hopefully should be posted later today.
sourcecodeplz 9 hours ago||
PHP 8.3.36 (cli) (built: Oct 21 2026 08:18:34) (NTS)

made it in time hopefully

dhruvagoyal 7 hours ago||
there is clearly some drama w.r.t. who takes credit here, 3 companies credited for a single flaw is super odd.
efesak 4 hours ago||
...and If you have a server in a closet still running PHP 5 or 7, hosting that project you’ll rewrite “next quarter,” this might buy you some time: https://github.com/analogic/phpsafepass
cowlevel 11 hours ago|
So they've added malloc fail checks and tests for malloc fail throughout.

Is this even reachable on Linux due to overcommit? Maybe by attempting a single extremely large allocation?

antiloper 11 hours ago|
PHP is tracking its own memory usage internally with limits configurable via php.ini.
More comments...