Loading vulnerability…
CVE-2022-31629 affects PHP before 7.4.31, 8.0.24, and 8.1.11. The flaw allows a network attacker or same-site attacker to set a standard insecure cookie in a victim's browser that is subsequently treated by PHP applications as a cookie using the special __Host- or __Secure- prefix semantics. This results in incorrect trust being placed in a cookie that did not satisfy the security properties normally associated with those prefixes, undermining application assumptions about cookie origin and transport security.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (POC) for CVE-2022-31629, a vulnerability in PHP's cookie handling that can allow CSRF token bypass. The repository contains Dockerfiles for PHP 8.1.10 and 8.1.11, an Nginx configuration for SSL termination, and a simple PHP web application (index.php) that demonstrates CSRF protection using the __Host-xsrf cookie. The exploit is performed via JavaScript in the browser, which sets a malformed cookie ('..Host-xsrf') and submits a POST request, attempting to bypass the CSRF check. The environment is orchestrated with docker-compose, exposing the application on HTTPS ports 8110 and 8111 for the two PHP versions. The repository is structured for easy testing and demonstration of the vulnerability, with endpoints at https://localhost:8110 and https://localhost:8111. No weaponized payload is included; the code is intended for demonstration and research purposes.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.