Loading vulnerability…
In Pallets Werkzeug versions 2.1.0 and below, improper parsing of HTTP requests allows attackers to perform HTTP Request Smuggling by sending specially crafted HTTP requests containing multiple requests within the body. This vulnerability arises due to the way Werkzeug parses HTTP requests, potentially allowing an attacker to bypass security controls or interfere with request processing when used in certain unsupported configurations.
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 provides a proof-of-concept (PoC) exploit for CVE-2022-29361, a client-side HTTP desynchronization vulnerability in Werkzeug 2.1.0 (used by Flask). The structure includes two main components: a 'vulnerable' Flask application running Werkzeug 2.1.0, and a 'poc' exploit server, both containerized via Docker. The exploit works by submitting a specially crafted POST request from the exploit server to the vulnerable server, leveraging a browser-based attack vector to trigger XSS. The main exploit logic is in 'poc/src/app.py', which serves a form and JavaScript to automate the attack. The endpoints involved are local HTTP servers on ports 5000 (exploit) and 5001 (vulnerable). The repository is well-structured for demonstration and testing, with clear separation between the vulnerable target and the exploit code.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.