Menu

PHP2Shell on a mixed fleet: auditing 5.6 to 8.4 and proving each build is actually patched
πŸ“°

PHP2Shell on a mixed fleet: auditing 5.6 to 8.4 and proving each build is actually patched

DEV Community: securityΒ·bitpageΒ·6 days ago
#venpH4mZ
#devtosecurity#devto#dev#patch#branch
Reading 0:00
15s threshold

Short answer: for PHP 8.2 and newer, a patched build is provable statically. The fixed releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12 introduce a new INI directive, memory_hard_limit_percent , which exists in none of their predecessors. For every branch from 5.6 through 8.1 there is no fixed release and no version change, so the only proof is behavioural: on a patched build an out-of-memory condition terminates the worker with exit code 1 and skips register_shutdown_function , where an unpatched build exits 255 and runs it.

PHP2Shell is two linked CVEs, published 21 October 2026 and fixed in releases dated the 22nd. The part that made it expensive was not the patching. It was answering, machine by machine, a question that normally takes one command: is this PHP fixed or not.

TL;DR

Fix: stay on the branch, move to the last patch release of that branch, then apply the patch.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.