CVE-2019-9511, also known as the HTTP/2 Data Dribble vulnerability, is an uncontrolled resource-consumption flaw affecting certain HTTP/2 server implementations. A remote client requests a large resource through multiple HTTP/2 streams, then manipulates flow-control window sizes and stream priorities to make the server buffer and queue response data in one-byte chunks. Inefficient queuing of these fragmented response units can consume excessive CPU, memory, or both.
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 2 candidates 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.
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Undertow HTTP/2 denial-of-service flaw triggered by a large volume of data requests.
HTTP/2 denial-of-service vulnerability involving excessive data requests.
An Undertow HTTP/2 denial-of-service vulnerability in which a large volume of data requests can exhaust resources.
An HTTP/2 denial-of-service flaw in Node.js in which requests carrying large amounts of data can exhaust resources.
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.