Loading vulnerability…
CVE-2014-0230 is an uncontrolled resource-consumption vulnerability in Apache Tomcat. When Tomcat sends an HTTP response before it has finished reading the complete request body, it can improperly retain the associated connection. A remote attacker can repeatedly initiate and abort uploads with sufficiently large request bodies, causing server threads or available connections to remain consumed. The issue affects Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.55, and 8.x before 8.0.9.
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.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A non-persistent denial-of-service flaw in Apache Tomcat that permits remote exhaustion of available server connections using a sufficiently large request body.
A remote denial-of-service vulnerability in Apache Tomcat where handling a sufficiently large request body can leave connections open and exhaust the available connection pool.
A specific CVE referenced by the Tomcat security advisory; the advisory content provides no vulnerability details.
A remote denial-of-service vulnerability in Apache Tomcat's handling of incomplete request bodies when a response is sent before the body is fully read. Repeated aborted upload attempts can consume server threads.
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.