CVE-2014-0075

MEDIUMCVSS v2 · 5.05.0
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 5.0 — NVD rates that MEDIUM (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:P. 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 18% 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
Elevated
5.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 18%CVSS v2: 5.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Integer overflow in the parseChunkHeader function in java/org/apache/coyote/http11/filters/ChunkedInputFilter.java in Apache Tomcat before 6.0.40, 7.x before 7.0.53, and 8.x before 8.0.4 allows remote attackers to cause a denial of service (resource consumption) via a malformed chunk size in chunked transfer coding of a request during the streaming of data.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
54
EG Risk 54/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)
Severity50% × 45%
Impact severity (EG Severity): CVSS 5.0 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
18%
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 (5.0): severity, escalated by confirmed exploitation. This CVE's 5.0 is its impact severity (EG Severity), not escalated.

EG Severity
5.0 MEDIUMCVSS-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:P
EG Likelihood
18% within 30 daysSource: FIRST EPSS. 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: 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.

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

May 31, 2014

Last Modified

October 14, 2026

References (48)

15 of 48 shown · show the other 33

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntutomcat7-user (7.0.52-1ubuntu0.1) @ trusty2026-10-14ubuntu
redhatjbossweb2015-05-14redhat
redhatpatch2015-03-11redhat
redhatpatch2014-09-03redhat
redhattomcat6-0:6.0.24-72.el6_52014-07-09redhat
redhatpatch2014-07-07redhat
redhatjbossweb-0:7.3.2-4.Final_redhat_3.1.ep6.el62014-07-07redhat
redhattomcat7-0:7.0.40-11_patch_03.ep6.el62014-07-03redhat
redhattomcat72014-07-03redhat
redhattomcat6-0:6.0.37-29_patch_05.ep6.el62014-07-03redhat
redhattomcat62014-07-03redhat
redhattomcat-0:7.0.42-6.el7_02014-07-02redhat

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 2 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.apache.tomcat:tomcat8.0.1, 8.0.3
  • every version up to 6.0.40: fixed in 6.0.40
  • 7.0.0 up to 7.0.53: fixed in 7.0.53
  • 8.0.0 up to 8.0.4: fixed in 8.0.4
—
org.apache.tomcat:tomcat-coyote8.0.1, 8.0.3
  • every version up to 6.0.40: fixed in 6.0.40
  • 7.0.0 up to 7.0.53: fixed in 7.0.53
  • 8.0.0 up to 8.0.4: fixed in 8.0.4
—
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
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 30× 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 90 of 140 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. 10 repeat rows among the latest 100 are merged into the row they repeat. The 50 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2014-0075?
CVE-2014-0075 is a medium-severity vulnerability; its CVE record was published on May 31, 2014. Integer overflow in the parseChunkHeader function in java/org/apache/coyote/http11/filters/ChunkedInputFilter.java in Apache Tomcat before 6.0.40, 7.x before 7.0.53, and 8.x before 8.0.4 allows remote attackers to cause a denial of service (resource consumption) via a malformed chunk size in…
When was CVE-2014-0075 made public?
CVE-2014-0075 was made public on May 27, 2014: 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 May 31, 2014. 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-0075 actively exploited?
CVE-2014-0075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
How do I remediate CVE-2014-0075?
A fix for CVE-2014-0075 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2014-0075 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-0075

Explore →

Is Your Infrastructure Affected by CVE-2014-0075?

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