Loading vulnerability…
CVE-2019-9517, known as Internal Data Buffering, is an HTTP/2 uncontrolled-resource-consumption vulnerability affecting implementations that queue response data without adequately constraining buffering when transport-layer transmission is blocked. A remote client advertises an open HTTP/2 flow-control window, preventing HTTP/2 flow control from limiting response generation, while withholding TCP receive-window capacity so response bytes cannot be transmitted. The client then requests large response objects, causing affected servers to queue blocked response data and consume excessive memory, CPU, or both. In Apache HTTP Server mod_http2, the condition can exhaust HTTP/2 worker capacity.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remotely reachable, low-complexity vulnerability requiring no privileges or user interaction, with high availability impact and no stated confidentiality or integrity impact.
An Undertow HTTP/2 denial-of-service vulnerability triggered by a request for a large response.
An HTTP/2 denial-of-service vulnerability in Node.js caused by requests for large responses.
An HTTP/2 denial-of-service vulnerability in which a request for a large response can consume excessive 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.