CVE-2008-2370

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:N/A:N. 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 52.7% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
5.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 204 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 53%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 53%CVSS v2: 5.0Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: 204

A fix is available — apply it.

Apache Tomcat 4.1.0 through 4.1.37, 5.5.0 through 5.5.26, and 6.0.0 through 6.0.16, when a RequestDispatcher is used, performs path normalization before removing the query string from the URI, which allows remote attackers to conduct directory traversal attacks and read arbitrary files via a .. (dot dot) in a request parameter.

Internet exposure · derived from Shodan data

204 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2008-2370, in our KEV-Exposure radar’s Shodan-derived sample.

across 24 countries (United States, China, Singapore, Germany, Japan)top: tomcat
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
53
EG Risk 53/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity50% × 45%
Exploitation65% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
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
53%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

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

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2008

Last Modified

April 23, 2026

References (120)

Vendor Advisories for CVE-2008-2370(1)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatxml-commons-0:1.3.02-2jpp_1rh2010-08-04redhat
redhattomcat5-0:5.0.30-0jpp_12rh2008-12-08redhat
redhattomcat5-0:5.5.23-0jpp_12rh2008-10-02redhat
redhattomcat5-0:5.5.23-0jpp_4rh.92008-10-02redhat
redhatjbossweb-0:2.0.0-5.CP07.0jpp.ep1.1.el52008-09-22redhat
redhattomcat5-0:5.5.23-0jpp.7.el5_2.12008-08-27redhat

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.tomcat:tomcat—
  • 4.1.0 up to 4.1.38: fixed in 4.1.38
  • 5.5.0 up to 5.5.27: fixed in 5.5.27
  • 6.0.0 up to 6.0.18: fixed in 6.0.18
—

Additional Vendor Advisories

(5)

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 6× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-09 20:00 UTCEPSS rescore
  2. 2026-10-08 16:33 UTCEPSS rescore
  3. 2026-10-07 23:37 UTCEPSS rescore
  4. 2026-10-06 15:09 UTCEPSS rescore
  5. 2026-10-05 17:37 UTCEPSS rescore
  6. 2026-10-03 14:20 UTCEPSS rescore
  7. 2026-10-01 19:42 UTCEPSS rescore
  8. 2026-09-30 14:57 UTCEPSS rescore
  9. 2026-09-29 07:49 UTCEG score recompute
  10. 2026-09-26 15:52 UTCEPSS rescore
  11. 2026-09-18 19:20 UTCEPSS rescore
  12. 2026-09-17 19:20 UTCEPSS rescore
  13. 2026-09-15 03:04 UTCEPSS rescore
  14. 2026-09-13 16:40 UTCEPSS rescore
  15. 2026-09-12 14:54 UTCEPSS rescore
  16. 2026-09-10 09:24 UTCEPSS rescore
  17. 2026-09-06 13:41 UTCEPSS rescore
  18. 2026-09-05 15:22 UTCEPSS rescore
  19. 2026-09-04 13:55 UTCEPSS rescore
  20. 2026-08-30 01:14 UTCEPSS rescore
  21. 2026-08-28 21:34 UTCEPSS rescore
  22. 2026-08-15 01:24 UTCEPSS rescore
  23. 2026-08-08 16:31 UTCEPSS rescore
  24. 2026-08-07 16:21 UTCEPSS rescore
  25. 2026-08-06 13:41 UTCEPSS rescore
Show 70 more
  1. 2026-08-04 15:03 UTCEPSS rescore
  2. 2026-08-03 10:28 UTCEPSS rescore
  3. 2026-07-30 01:25 UTCEPSS rescore
  4. 2026-07-26 13:35 UTCEG score recompute▲ 5.00
  5. 2026-07-25 14:12 UTCEPSS rescore
  6. 2026-07-24 14:12 UTCEPSS rescore
  7. 2026-07-23 14:14 UTCEPSS rescore
  8. 2026-07-23 00:56 UTCEG score recompute
  9. 2026-07-23 00:34 UTCEG score recompute▼ 3.70
  10. 2026-07-23 00:01 UTCEG score recompute▲ 3.70
  11. 2026-07-22 21:40 UTCEG score recompute▼ 9.00
  12. 2026-07-20 17:03 UTCEPSS rescore
  13. 2026-07-16 16:58 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-13 22:25 UTCEPSS rescore
  17. 2026-07-13 06:07 UTCEPSS rescore
  18. 2026-07-11 08:22 UTCEPSS rescore
  19. 2026-07-11 08:22 UTCEPSS rescore
  20. 2026-07-09 19:04 UTCEPSS rescore
  21. 2026-07-06 16:23 UTCEPSS rescore
  22. 2026-07-06 02:19 UTCEPSS rescore
  23. 2026-07-06 02:19 UTCEPSS rescore
  24. 2026-07-02 14:00 UTCEPSS rescore
  25. 2026-07-01 15:02 UTCEPSS rescore
  26. 2026-07-01 15:02 UTCEPSS rescore
  27. 2026-06-28 04:52 UTCEPSS rescore
  28. 2026-06-27 03:04 UTCEPSS rescore
  29. 2026-06-25 13:46 UTCEPSS rescore
  30. 2026-06-25 13:46 UTCEPSS rescore
  31. 2026-06-24 14:02 UTCEPSS rescore
  32. 2026-06-24 14:02 UTCEPSS rescore
  33. 2026-06-23 21:29 UTCEPSS rescore
  34. 2026-06-23 21:29 UTCEPSS rescore
  35. 2026-06-21 01:56 UTCEPSS rescore
  36. 2026-06-21 01:56 UTCEPSS rescore
  37. 2026-06-18 17:49 UTCEPSS rescore
  38. 2026-06-18 17:49 UTCEPSS rescore
  39. 2026-06-17 17:49 UTCEPSS rescore
  40. 2026-06-17 17:49 UTCEPSS rescore
  41. 2026-06-16 17:49 UTCEPSS rescore
  42. 2026-06-16 17:49 UTCEPSS rescore
  43. 2026-06-15 17:44 UTCEPSS rescore
  44. 2026-06-14 23:13 UTCEPSS rescore
  45. 2026-06-12 23:08 UTCEPSS rescore
  46. 2026-06-12 23:08 UTCEPSS rescore
  47. 2026-06-10 22:14 UTCEPSS rescore
  48. 2026-06-10 13:17 UTCEPSS rescore
  49. 2026-06-08 14:13 UTCEPSS rescore
  50. 2026-06-07 15:22 UTCEPSS rescore
  51. 2026-06-05 22:44 UTCEPSS rescore
  52. 2026-06-05 22:44 UTCEPSS rescore
  53. 2026-06-05 06:07 UTCEPSS rescore
  54. 2026-06-04 13:09 UTCEPSS rescore
  55. 2026-06-04 13:09 UTCEPSS rescore
  56. 2026-06-01 13:49 UTCEPSS rescore
  57. 2026-06-01 13:49 UTCEPSS rescore
  58. 2026-06-01 13:49 UTCEPSS rescore
  59. 2026-05-30 20:47 UTCEG score recompute
  60. 2026-05-30 20:47 UTCVendor advisory
  61. 2026-05-29 13:40 UTCEPSS rescore
  62. 2026-05-28 13:42 UTCEPSS rescore
  63. 2026-05-28 13:42 UTCEPSS rescore
  64. 2026-05-28 13:42 UTCEPSS rescore
  65. 2026-05-26 07:16 UTCEPSS rescore
  66. 2026-05-26 07:16 UTCEPSS rescore
  67. 2026-05-24 16:43 UTCEPSS rescore
  68. 2026-05-22 21:15 UTCEPSS rescore
  69. 2026-05-22 21:15 UTCEPSS rescore
  70. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-32137✓ verified
    First seen Aug 1, 2008

    Apache Tomcat 6.0.16 - 'RequestDispatcher' Information Disclosure

    Open source ↗

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2008-2370?
CVE-2008-2370 is a medium vulnerability published on August 4, 2008. Apache Tomcat 4.1.0 through 4.1.37, 5.5.0 through 5.5.26, and 6.0.0 through 6.0.16, when a RequestDispatcher is used, performs path normalization before removing the query string from the URI, which allows remote attackers to conduct directory traversal attacks and read arbitrary files via a ..…
When was CVE-2008-2370 disclosed?
CVE-2008-2370 was first published on August 4, 2008, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2008-2370 actively exploited?
CVE-2008-2370 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 53% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-2370?
A fix for CVE-2008-2370 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2008-2370 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-2008-2370

Explore →

Is Your Infrastructure Affected by CVE-2008-2370?

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

Book a Demo →Browse All CVEs