CVE-2014-0230

HIGHCVSS v2 · 7.87.8
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.8 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:N/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 20% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Trending — 4 sources updated this weekElevated

Also known asEUVD-2022-4851 (ENISA EUVD) · GHSA-pxcx-cxq8-4mmw (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 20%CVSS v2: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v2.0 (legacy)
7.8HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.8HIGHlow confidence
EG Risk
66
EG Risk 66/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
20%
EPSS %ILE
97th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:N/AC:L/Au:N/C:N/I:N/A:C
EG Likelihood
20% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 7, 2015

Last Modified

October 14, 2026

References (39)

15 of 39 shown · show the other 24

Vendor Advisories for CVE-2014-0230(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibtomcat6-java (6.0.35-1ubuntu3.6) @ precise2026-10-29ubuntu
ubuntulibtomcat7-java (7.0.56-2ubuntu0.1) @ vivid2026-10-29ubuntu
redhattomcat-0:7.0.69-10.el72016-11-03redhat
redhatpatch2016-04-05redhat
redhatweld-core-0:1.1.33-1.Final_redhat_1.1.ep6.el52016-04-05redhat
redhatjboss-ec2-eap-0:7.5.7-2.Final_redhat_3.ep6.el62016-04-05redhat
redhatweld-core-0:1.1.33-1.Final_redhat_1.1.ep6.el62016-04-05redhat
redhatweld-core-0:1.1.33-1.Final_redhat_1.1.ep6.el72016-04-05redhat
redhattomcat-vault-0:1.0.8-4.Final_redhat_4.1.ep7.el62015-12-16redhat
redhatpatch2015-12-16redhat
redhattomcat-vault-0:1.0.8-4.Final_redhat_4.1.ep7.el72015-12-16redhat
redhattomcat8-0:8.0.18-25_patch_00.ep7.el72015-09-10redhat
redhattomcat8-0:8.0.18-25_patch_00.ep7.el62015-09-10redhat
redhattomcat7-0:7.0.54-20_patch_04.ep6.el72015-08-13redhat
redhatpatch2015-08-13redhat
mavenorg.apache.tomcat:tomcat @ 6.0.44 (fixes >= 6.0.0, < 6.0.44)—ghsa
mavenorg.apache.tomcat:tomcat @ 7.0.55 (fixes >= 7.0.0, < 7.0.55)—ghsa
mavenorg.apache.tomcat:tomcat @ 8.0.9 (fixes >= 8.0.0, < 8.0.9)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
tomcat66.0.28-10 ... 6.0.41-2+squeeze6 (28 versions)
  • every version up to 6.0.41-2+squeeze7: fixed in 6.0.41-2+squeeze7
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
tomcat66.0.35-6 ... 6.0.45-1~deb6u1 (13 versions)
  • every version up to 6.0.45+dfsg-1~deb7u1: fixed in 6.0.45+dfsg-1~deb7u1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.tomcat:tomcat8.0.1, 8.0.3, 8.0.5, 8.0.8
  • 6.0.0 up to 6.0.44: fixed in 6.0.44
  • 7.0.0 up to 7.0.55: fixed in 7.0.55
  • 8.0.0 up to 8.0.9: fixed in 8.0.9
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 11× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 166 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 71 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  2. 2026-11-01 08:49 UTCGHSA enrichmentGHSA-pxcx-cxq8-4mmw · GitHub severity HIGH
  3. 2026-11-01 08:49 UTCEG score recompute
  4. 2026-10-31 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  5. 2026-10-30 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  6. 2026-10-29 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  7. 2026-10-29 05:29 UTCEG score recompute
  8. 2026-10-29 05:29 UTCVendor advisory
  9. 2026-10-28 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  10. 2026-10-27 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  11. 2026-10-26 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  12. 2026-10-25 20:05 UTCEG score recompute
  13. 2026-10-25 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  14. 2026-10-24 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  15. 2026-10-23 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  16. 2026-10-22 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  17. 2026-10-22 09:31 UTCEG score recompute
  18. 2026-10-22 09:31 UTCVendor advisory
  19. 2026-10-21 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  20. 2026-10-20 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  21. 2026-10-19 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  22. 2026-10-18 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  23. 2026-10-18 11:15 UTCEG score recompute
  24. 2026-10-17 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  25. 2026-10-16 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
Show 70 more
  1. 2026-10-15 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  2. 2026-10-14 18:46 UTCEG score recompute
  3. 2026-10-14 18:46 UTCVendor advisory
  4. 2026-10-14 17:25 UTCNVD update
  5. 2026-10-14 16:29 UTCMITRE cvelistV5
  6. 2026-10-14 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  7. 2026-10-13 16:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  8. 2026-10-12 21:20 UTCEG score recompute
  9. 2026-10-12 16:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  10. 2026-10-12 01:28 UTCEG score recompute
  11. 2026-10-11 13:39 UTCEPSS rescoreEPSS 20% · 97th percentile
  12. 2026-10-10 19:54 UTCEPSS rescoreEPSS 20% · 97th percentile
  13. 2026-10-09 20:01 UTCEPSS rescoreEPSS 20% · 97th percentile
  14. 2026-10-08 16:34 UTCEPSS rescoreEPSS 20% · 97th percentile
  15. 2026-10-07 23:39 UTCEPSS rescoreEPSS 20% · 97th percentile
  16. 2026-10-06 15:11 UTCEPSS rescoreEPSS 20% · 97th percentile
  17. 2026-09-30 14:58 UTCEPSS rescoreEPSS 20% · 97th percentile
  18. 2026-09-30 00:18 UTCEG score recompute
  19. 2026-09-27 13:39 UTCEPSS rescoreEPSS 20% · 97th percentile
  20. 2026-09-26 15:53 UTCEPSS rescoreEPSS 20% · 97th percentile
  21. 2026-09-21 20:25 UTCEPSS rescoreEPSS 20% · 97th percentile
  22. 2026-09-18 19:21 UTCEPSS rescoreEPSS 20% · 97th percentile
  23. 2026-09-17 19:21 UTCEPSS rescoreEPSS 20% · 97th percentile
  24. 2026-09-15 03:04 UTCEPSS rescoreEPSS 20% · 97th percentile
  25. 2026-09-12 14:55 UTCEPSS rescoreEPSS 20% · 97th percentile
  26. 2026-09-11 09:30 UTCEPSS rescoreEPSS 20% · 97th percentile
  27. 2026-09-07 15:56 UTCEPSS rescoreEPSS 20% · 97th percentile
  28. 2026-09-04 13:55 UTCEPSS rescoreEPSS 20% · 97th percentile
  29. 2026-08-30 19:12 UTCEPSS rescoreEPSS 20% · 97th percentile
  30. 2026-08-27 14:20 UTCEPSS rescoreEPSS 20% · 97th percentile
  31. 2026-08-26 14:41 UTCEPSS rescoreEPSS 20% · 97th percentile
  32. 2026-08-25 13:43 UTCEPSS rescoreEPSS 20% · 97th percentile
  33. 2026-08-23 00:13 UTCEPSS rescoreEPSS 20% · 97th percentile
  34. 2026-08-21 23:44 UTCEPSS rescoreEPSS 20% · 97th percentile
  35. 2026-08-20 22:50 UTCEPSS rescoreEPSS 20% · 97th percentile
  36. 2026-08-19 16:59 UTCEPSS rescoreEPSS 20% · 97th percentile
  37. 2026-08-18 13:43 UTCEPSS rescoreEPSS 20% · 97th percentile
  38. 2026-08-16 14:50 UTCEPSS rescoreEPSS 20% · 97th percentile
  39. 2026-08-16 02:09 UTCEPSS rescoreEPSS 20% · 97th percentile
  40. 2026-08-15 01:25 UTCEPSS rescoreEPSS 20% · 97th percentile
  41. 2026-08-07 16:21 UTCEPSS rescoreEPSS 20% · 97th percentile
  42. 2026-08-06 13:42 UTCEPSS rescoreEPSS 20% · 97th percentile
  43. 2026-08-05 19:12 UTCEPSS rescoreEPSS 20% · 97th percentile
  44. 2026-08-04 15:04 UTCEPSS rescoreEPSS 20% · 97th percentile
  45. 2026-08-01 04:11 UTCEPSS rescoreEPSS 20% · 97th percentile
  46. 2026-07-30 16:23 UTCEPSS rescoreEPSS 20% · 97th percentile
  47. 2026-07-28 15:31 UTCEPSS rescoreEPSS 20% · 97th percentile
  48. 2026-07-26 13:49 UTCEG score recomputeFirst assessed: 7.8 HIGH
  49. 2026-07-23 14:14 UTCEPSS rescoreEPSS 20% · 97th percentile
  50. 2026-07-23 01:11 UTCEG score recompute
  51. 2026-07-23 00:15 UTCEG score recompute
  52. 2026-07-22 21:53 UTCEG score recompute
  53. 2026-07-22 14:04 UTCEPSS rescoreEPSS 20% · 97th percentile
  54. 2026-07-21 15:21 UTCEPSS rescoreEPSS 20% · 97th percentile
  55. 2026-07-20 17:03 UTCEPSS rescoreEPSS 20% · 97th percentile
  56. 2026-07-19 14:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  57. 2026-07-19 02:25 UTCEPSS rescoreEPSS 20% · 97th percentile
  58. 2026-07-18 10:00 UTCEPSS rescoreEPSS 20% · 97th percentile
  59. 2026-07-16 16:58 UTCEPSS rescoreEPSS 20% · 97th percentile
  60. 2026-07-15 16:54 UTCEPSS rescoreEPSS 20% · 97th percentile
  61. 2026-07-13 22:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  62. 2026-07-13 06:08 UTCEPSS rescoreEPSS 20% · 97th percentile
  63. 2026-07-12 05:42 UTCEPSS rescoreEPSS 20% · 97th percentile
  64. 2026-07-09 19:05 UTCEPSS rescoreEPSS 20% · 97th percentile
  65. 2026-07-08 15:10 UTCEPSS rescoreEPSS 20% · 97th percentile
  66. 2026-07-07 13:41 UTCEPSS rescoreEPSS 20% · 97th percentile
  67. 2026-07-06 02:19 UTCEPSS rescoreEPSS 20% · 97th percentile
  68. 2026-07-05 02:26 UTCEPSS rescoreEPSS 20% · 97th percentile
  69. 2026-07-04 06:27 UTCEPSS rescoreEPSS 20% · 97th percentile
  70. 2026-07-02 15:21 UTCEPSS rescoreEPSS 20% · 97th percentile

Frequently asked(4)

What is CVE-2014-0230?
CVE-2014-0230 is a high-severity vulnerability; its CVE record was published on June 7, 2015. 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…
When was CVE-2014-0230 made public?
CVE-2014-0230 was made public on April 9, 2015: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on June 7, 2015. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2014-0230 actively exploited?
CVE-2014-0230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
How do I remediate CVE-2014-0230?
A fix for CVE-2014-0230 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2014-0230 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-0230

Explore →

Is Your Infrastructure Affected by CVE-2014-0230?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.