CVE-2024-22201 is a resource-leak vulnerability in Jetty's HTTP/2 TLS connection handling. When an established HTTP/2 TLS connection is TCP-congested and subsequently times out, affected Jetty versions can fail to close and release the connection's file descriptor. An unauthenticated attacker can repeatedly induce this condition, accumulating leaked established connections until available file descriptors are exhausted.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Jetty vulnerability in which valid clients can cause the service to stop accepting new connections.
A Jetty vulnerability described as allowing valid clients to prevent acceptance of new connections, addressed in the OpenShift Jenkins security update.
A Jetty vulnerability that can cause the server to stop accepting new connections from valid clients.
A Jetty vulnerability that can cause the server to stop accepting new connections from valid clients.
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.