Elektrine lite

← Feed

@hasamba@infosec.exchange

2026-10-23 08:37 UTC

---------------- 🛠️ Tool =================== php2shell-scanner: high-fidelity exposure detection for CVE-2026-109618 and CVE-2026-109619 Searchlight Cyber's research team (the group formerly known as Assetnote) released an open-source scanner for the php2shell vulnerability pair. The team has been through this cycle before, both with wp2shell, which it discovered itself, and with react2shell late last year. Each of these high-impact web-stack issues raises the same detection problem: maximize coverage while minimizing false positives and false negatives. This release is their answer for the current one. Why another scanner Scanners published in the wake of the disclosure mostly rely on version checks, or fail to represent the vulnerable conditions accurately for both mod_php and php-fpm. Version-only signals fail in two directions: flagging hosts that are actually patched, or missing hosts where the banner does not reflect exploitable conditions. The logic was first implemented inside the Searchlight Exposure platform, and the standalone version is now public. How the check works Detection is progressive, in three tiers: 1. Controlled OOM trigger. The scanner attempts to produce a PHP memory-exhaustion error. The vulnerability fundamentally requires an out-of-memory condition, so there is no reliable way to confirm exploitability without inducing it. 2. Differential empty HTTP 500. Next, it observes responses for a differential empty HTTP 500, which the authors describe as a PHP-FPM worker failure. 3. Version fallback. Only when behavioral checks do not settle the question does it fall back to whether the target advertises a known unpatched PHP version. Risk profile The authors are direct about this: triggering an OOM condition is inherently risky, and that is the price of reliable detection here. In the majority of PHP installations a worker crash recovers quickly and should not cause disruption, but the writeup explicitly asks for care and caution when scanning. Practical translation: don't fire this at capacity-constrained production systems during peak traffic. Context around the disclosure Initial information on the vulnerability was incomplete, followed quickly by a wave of auto-generated, low-quality PoCs that added noise rather than clarity. Searchlight credits Calif's writeup with settling most of the open questions. The detection logic served Searchlight Exposure customers first, then was released publicly so anyone can determine exposure with the same rigor. Practical notes • Exposure validation across mixed PHP estates where mod_php and php-fpm behave differently • Prioritization: behavioral tiers are stronger evidence than version matches • Scheduling: run behavioral checks away from peak load, and treat the version fallback tier as weaker evidence by design • The tool is newly released and not personally tested; this summary reflects the vendor writeup, not an independent accuracy assessment References • Repository: assetnote/php2shell-scanner on GitHub • Authors: Shubham Shah, Adam Kues, Patrik Grobshäuser, Kevin Gervot • Related: Calif's writeup on php2shell 🔹 tool #php2shell #cve_2026_109618 #cve_2026_109619 #phpfpm 🔗 Source: https://www.slcyber.io/research/high-fidelity-detection-mechanism-for-php2shell-cve-2026-109618-and-cve-2026-109619

Replies (0)

No replies.