Repository navigation
Report incomplete process inspection instead of a clean stale-worker check - #1
artifexignotvs wants to merge 1 commit into
Conversation
|
Merged as afdfc06 and released in 3.0.0. Thank you — this closed a real gap, We reproduced the original problem before merging, in an unmodified Because that is the normal state of a run inside a container rather than a rare Then the Alpine job of the matrix turned red on your own case "Apache maps read Changed on merge: rebased onto main (2.1.1 at the time), and Closing this because it landed under a different commit id, not because |
Root inside a container may lack permission to inspect PHP workers even when its effective UID is zero. The stale-process check currently skips failed reads of
/proc/<pid>/exeand can report the process check asokdespite visible PHP workers that it could not inspect.This change records an
unknownprocess finding for recognized PHP/Apache processes with inaccessible executable links, or Apache processes whose maps cannot be read. It preserves existing restart warnings, avoids anokfinding when inspection is incomplete, ignores zombies and processes that have disappeared, and uses the existingP2S_PROC_ROOThook for deterministic regression cases. The existing summary logic then returnsundecided/ exit 2.Reproduced in an isolated Ubuntu 24.04 container with
php8.3-fpm 8.3.6-0ubuntu0.24.04.13. With three stable FPM processes and UID 0, droppingSYS_PTRACEmade all three executable links unreadable. On the same process identities, the original script reportednot-vulnerable/ processok/ exit 0; the patched script reportedundecided/ processunknown/ exit 2. With inspection permission present, the patched script retained processok/ exit 0. No exploit requests were used.Validation:
This does not establish coverage of hidden PIDs or renamed runtimes; it prevents known inspection failures from being treated as successful process checks.