Loading vulnerability…
CVE-2019-9513, known as Resource Loop, is an HTTP/2 resource-exhaustion vulnerability affecting susceptible HTTP/2 implementations. An attacker opens multiple request streams and repeatedly changes their priorities, causing substantial churn in the HTTP/2 priority tree. Processing the resulting PRIORITY-frame flood can consume excessive CPU resources and deny service to legitimate clients.
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.
20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Undertow HTTP/2 denial-of-service vulnerability caused by PRIORITY-frame flooding and excessive resource consumption.
An HTTP/2 denial-of-service flaw in Node.js where PRIORITY-frame flooding causes excessive resource consumption.
An HTTP/2 denial-of-service vulnerability where flooding with PRIORITY frames causes excessive resource consumption.
An HTTP/2 denial-of-service vulnerability in Node.js in which PRIORITY-frame floods cause excessive resource consumption.
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.