PHP patches seven critical flaws that can lead to code execution
Fixes are in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; several bugs need specific application conditions.
Timezone cache use-after-free can lead to remote code execution. In non-thread-safe builds, a diagnostic written to a file-based error_log during module startup, for example for an invalid date.timezone value or a session configuration warning, causes the timezone cache to be allocated in startup memory that is freed while a reference to it is kept. A diagnostic raised early in the first request of a worker, such as the max_input_vars warning, then accesses the freed cache. On such a deployment an unauthenticated remote attacker can crash PHP-FPM, Apache mod_php or CGI workers with a crafted request. Arbitrary code execution may be possible and has been demonstrated with known memory addresses. This issue affects PHP versions before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Fixes are in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; several bugs need specific application conditions.
Wiz reports no observed exploitation; PHP 8.1 and earlier receive no official fixes.
Fixed builds include PHP 8.6.0 and 8.5.13, plus 8.4.28, 8.3.37 and 8.2.36 for most issues.
The November 19 releases fix flaws that PHP says need non-default or uncommon setups, including session-handling remote code execution.
Fixed releases are PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36; two issues can reach ordinary WordPress hosts.
The top issue is a PHP-FPM request-smuggling flaw scored 9.2 that needs reused backend connections.
Fixes are in 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; maintainers say the critical bugs need uncommon setups.
Today 915 readers · 1K views · 86 reads · all time 211K views