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.
Use-after-free in PHP session shutdown without OPcache
PHP’s session extension keeps the executing script’s filename when a session starts. A fatal error in an application callback while session variables are destroyed at shutdown, such as stream_close() on a user-defined stream wrapper, can leave that pointer after request memory is freed. A later request on the same worker may free the stale string, crashing the worker or corrupting memory; code execution has not been demonstrated. This needs the filename in request memory, for example when OPcache does not cache the script, and affects PHP 8.3, 8.4, and 8.5 before the fixed releases.
What to do: Upgrade PHP to 8.3.37, 8.4.28, or 8.5.13, matching the installed branch.
| Product | Affected | Fixed in |
|---|---|---|
| PHP | 8.3.* before 8.3.37, 8.4.* before 8.4.28, and 8.5.* before 8.5.13 | 8.3.37, 8.4.28, and 8.5.13 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Use-after-free after interrupted session shutdown. The session extension records the filename of the executing script when a session starts. If a fatal error occurs in an application callback while the session variables are destroyed at shutdown, such as stream_close() of a user-defined stream wrapper, the pointer is retained after the request memory is freed, and a later request handled by the same worker can free the stale string. An attacker who can trigger such a failing cleanup may crash the worker or corrupt memory; code execution has not been demonstrated. This requires the filename to be allocated in request memory, for example when the script is not cached by OPcache. This issue affects PHP versions 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.
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