How severe is CVE-2014-0230?

No CVSS score has been assigned to CVE-2014-0230 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-0230?

CVE-2014-0230 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-0230?

Update org.apache.tomcat:tomcat to 6.0.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0230 is resolved across your whole dependency graph.

How do I detect CVE-2014-0230 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-0230 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2014-0230?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-0230 can be triaged on real exposure rather than presence alone.

Is CVE-2014-0230 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-0230 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-0230?

CVE-2014-0230 has an EPSS (Exploit Prediction Scoring System) score of 20.2%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2014-0230?

CVE-2014-0230 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0230 published, and has it been updated?

CVE-2014-0230 was published on May 14, 2022 and was last updated on December 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2014-0230 — tomcat

Fix: apache/tomcat@6b2cfac

CVE-2014-0230 is a CWE-399 vulnerability in org.apache.tomcat:tomcat. EPSS puts its 30-day exploitation probability at 20.2% (97th percentile). A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Uncontrolled Resource Consumption in Apache Tomcat

Published

May 14, 2022

Updated

Dec 7, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

20.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.55, and 8.x before 8.0.9 does not properly handle cases where an HTTP response occurs before finishing the reading of an entire request body, which allows remote attackers to cause a denial of service (thread consumption) via a series of aborted upload attempts.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.44	6.0.44`org.apache.tomcat:tomcat:6.0.44`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.55	7.0.55`org.apache.tomcat:tomcat:7.0.55`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0&&< 8.0.9	8.0.9`org.apache.tomcat:tomcat:8.0.9`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 6.0.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0230 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-0230 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-0230. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7	`tomcat-0:7.0.69-10.el7`	RHSA-2016:2599
Red Hat JBoss Enterprise Application Platform 6.4	see advisory	RHSA-2016:0599
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5	`glassfish-jsf-eap6-0:2.1.28-10.SP9_redhat_1.1.ep6.el5`	RHSA-2016:0595
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6	`glassfish-jsf-eap6-0:2.1.28-10.SP9_redhat_1.1.ep6.el6`	RHSA-2016:0596
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6	`jboss-ec2-eap-0:7.5.7-2.Final_redhat_3.ep6.el6`	RHSA-2016:0598
Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7	`glassfish-jsf-eap6-0:2.1.28-10.SP9_redhat_1.1.ep6.el7`	RHSA-2016:0597
Red Hat JBoss Enterprise Web Server 2 for RHEL 5	`tomcat6-0:6.0.41-15_patch_04.ep6.el5`	RHSA-2015:1622
Red Hat JBoss Web Server 2.1	see advisory	RHSA-2015:1621

Ubuntu

USN-2655-1Ubuntu USN-2654-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0230 in your dependencies?

O3 Security finds CVE-2014-0230 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works