Loading vulnerability…
CVE-2023-36478 is an integer-overflow vulnerability in Eclipse Jetty's HTTP/2 HPACK header processing. In Jetty 9.0.0 through 9.4.52, 10.0.0 through 10.0.15, and 11.0.0 through 11.0.15, MetaDataBuilder.checkSize performs an overflow-prone multiplication while estimating the decoded size of Huffman-encoded header names or values. A sufficiently large encoded length can overflow to a negative value, bypassing header-size-limit validation. The negative value can subsequently result in a very large buffer allocation when it is multiplied during later processing.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Jetty HTTP/2 HPACK header-value vulnerability that can cause denial of service.
An Eclipse Jetty denial-of-service vulnerability caused by integer overflow and buffer allocation issues in MetaDataBuilder.checkSize.
A command-execution flaw in Eclipse Jetty's CGI Servlet. Crafted binary names containing a quotation mark followed by a space can alter command tokenization when Jetty invokes Runtime.exec, potentially causing an unintended command to execute.
A Jetty HTTP/1 Content-Length parsing flaw in which Jetty accepted a leading plus sign (`+`) before the Content-Length value, contrary to RFC requirements. Parser discrepancies with a front-end or intermediary server could theoretically enable HTTP request smuggling.
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.