Loading vulnerability…
CVE-2017-2666 is an HTTP request/response smuggling vulnerability in Undertow caused by insufficient validation of invalid characters in the HTTP request line. When Undertow is deployed behind an intermediary proxy that also accepts the malformed characters but interprets them differently, an attacker can create a parsing discrepancy and inject attacker-controlled data into an HTTP response.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Prior Undertow vulnerability referenced solely because CVE-2020-10687 was an incomplete fix for it.
Prior Undertow vulnerability referenced only as the incomplete-fix predecessor to CVE-2020-10687.
Prior vulnerability cited as having been incompletely fixed by the issue addressed in CVE-2020-10687.
A previously addressed Undertow vulnerability whose fix was incomplete, leading to CVE-2020-10687.
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.