Loading vulnerability…
CVE-2022-41717 is an uncontrolled memory-consumption vulnerability in Go's HTTP/2 server implementation in net/http and golang.org/x/net/http2. HTTP/2 server connections maintain a cache of client-supplied HTTP header keys. Although the number of cache entries is bounded, header-key size was not sufficiently constrained for this cache. A client can send exceptionally large header keys and cause approximately 64 MiB of memory allocation for each open HTTP/2 connection.
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.
46 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Go net/http vulnerability that can cause excessive memory growth in a server accepting HTTP/2 requests.
A Go net/http vulnerability that permits excessive memory growth in a server accepting HTTP/2 requests, resulting in denial of service.
Go net/http vulnerability that can cause excessive memory growth in servers accepting HTTP/2 requests.
A Go vulnerability included in the Red Hat go-toolset and golang security-update advisory; no technical details are provided in the content.
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.