CVE-2008-0455

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — 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:M/Au:N/C:N/I:P/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 64.8% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
4.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 116 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 65%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 65%CVSS v2: 4.3Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: 116

A fix is available — apply it.

Cross-site scripting (XSS) vulnerability in the mod_negotiation module in the Apache HTTP Server 2.2.6 and earlier in the 2.2.x series, 2.0.61 and earlier in the 2.0.x series, and 1.3.39 and earlier in the 1.3.x series allows remote authenticated users to inject arbitrary web script or HTML by uploading a file with a name containing XSS sequences and a file extension, which leads to injection within a (1) "406 Not Acceptable" or (2) "300 Multiple Choices" HTTP response when the extension is omitted in a request for the file.

Internet exposure · derived from Shodan data

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

across 28 countries (United States, Japan, Germany, Canada, Italy)top: http_server
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)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3MEDIUMlow confidence
EG Risk
50
EG Risk 50/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
Severity43% × 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
65%
EPSS %ILE
99th
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

January 25, 2008

Last Modified

April 23, 2026

References (52)

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhathttpd-0:2.2.15-26.el62013-02-20redhat
redhathttpd-0:2.2.3-74.el52013-01-08redhat
redhatpatch2012-12-18redhat
redhatxom-0:1.2.7-1._redhat_3.1.ep6.el5.62012-12-18redhat
redhatxom-0:1.2.7-1._redhat_3.1.ep6.el6.62012-12-18redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-8: fixed in 2.2.22-8
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-8: fixed in 2.2.22-8
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-8: fixed in 2.2.22-8
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-8: fixed in 2.2.22-8
—

Weakness Classification(1)

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

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 11× 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-06 15:09 UTCEPSS rescore
  2. 2026-10-04 06:34 UTCOSV refresh
  3. 2026-10-03 14:20 UTCEPSS rescore
  4. 2026-10-01 19:42 UTCEPSS rescore
  5. 2026-09-30 14:57 UTCEPSS rescore
  6. 2026-09-29 07:47 UTCEG score recompute
  7. 2026-09-18 19:20 UTCEPSS rescore
  8. 2026-09-17 19:20 UTCEPSS rescore
  9. 2026-09-15 03:04 UTCEPSS rescore
  10. 2026-09-14 20:44 UTCOSV refresh
  11. 2026-09-12 14:54 UTCEPSS rescore
  12. 2026-09-05 15:22 UTCEPSS rescore
  13. 2026-09-04 04:59 UTCEPSS rescore
  14. 2026-08-30 01:14 UTCEPSS rescore
  15. 2026-08-26 20:03 UTCOSV refresh
  16. 2026-08-10 10:10 UTCOSV refresh
  17. 2026-08-07 16:20 UTCEPSS rescore
  18. 2026-08-05 19:11 UTCEPSS rescore
  19. 2026-07-30 16:22 UTCEPSS rescore
  20. 2026-07-30 01:25 UTCEPSS rescore
  21. 2026-07-28 15:30 UTCEPSS rescore
  22. 2026-07-26 13:34 UTCEG score recompute▲ 4.30
  23. 2026-07-25 14:12 UTCEPSS rescore
  24. 2026-07-25 10:41 UTCOSV refresh
  25. 2026-07-24 14:11 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 00:55 UTCEG score recompute
  2. 2026-07-23 00:34 UTCEG score recompute▼ 5.70
  3. 2026-07-23 00:00 UTCEG score recompute▲ 5.70
  4. 2026-07-22 21:39 UTCEG score recompute
  5. 2026-07-22 14:03 UTCEPSS rescore
  6. 2026-07-21 15:19 UTCEPSS rescore
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-16 16:58 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-11 08:22 UTCEPSS rescore
  12. 2026-07-08 05:35 UTCOSV refresh
  13. 2026-07-06 16:22 UTCEPSS rescore
  14. 2026-07-04 06:27 UTCEPSS rescore
  15. 2026-07-04 06:27 UTCEPSS rescore
  16. 2026-07-02 14:00 UTCEPSS rescore
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-29 14:02 UTCEPSS rescore
  20. 2026-06-29 14:02 UTCEPSS rescore
  21. 2026-06-28 14:03 UTCEPSS rescore
  22. 2026-06-28 04:52 UTCEPSS rescore
  23. 2026-06-27 03:04 UTCEPSS rescore
  24. 2026-06-25 13:46 UTCEPSS rescore
  25. 2026-06-25 13:46 UTCEPSS rescore
  26. 2026-06-23 21:29 UTCEPSS rescore
  27. 2026-06-23 21:29 UTCEPSS rescore
  28. 2026-06-19 17:25 UTCOSV refresh
  29. 2026-06-18 17:49 UTCEPSS rescore
  30. 2026-06-18 17:49 UTCEPSS rescore
  31. 2026-06-17 17:49 UTCEPSS rescore
  32. 2026-06-17 17:49 UTCEPSS rescore
  33. 2026-06-16 17:49 UTCEPSS rescore
  34. 2026-06-16 17:49 UTCEPSS rescore
  35. 2026-06-16 17:49 UTCEPSS rescore
  36. 2026-06-15 17:44 UTCEPSS rescore
  37. 2026-06-12 23:08 UTCEPSS rescore
  38. 2026-06-10 22:14 UTCEPSS rescore
  39. 2026-06-08 14:13 UTCEPSS rescore
  40. 2026-06-06 13:44 UTCEPSS rescore
  41. 2026-06-06 13:44 UTCEPSS rescore
  42. 2026-06-05 22:44 UTCEPSS rescore
  43. 2026-06-05 22:44 UTCEPSS rescore
  44. 2026-06-04 13:09 UTCEPSS rescore
  45. 2026-06-04 13:09 UTCEPSS rescore
  46. 2026-06-04 13:09 UTCEPSS rescore
  47. 2026-06-02 20:10 UTCEPSS rescore
  48. 2026-06-02 20:10 UTCEPSS rescore
  49. 2026-06-01 13:49 UTCEPSS rescore
  50. 2026-06-01 13:49 UTCEPSS rescore
  51. 2026-06-01 13:49 UTCEPSS rescore
  52. 2026-05-31 22:28 UTCEPSS rescore
  53. 2026-05-31 22:28 UTCEPSS rescore
  54. 2026-05-31 00:13 UTCEPSS rescore
  55. 2026-05-31 00:13 UTCEPSS rescore
  56. 2026-05-30 23:13 UTCEG score recompute
  57. 2026-05-30 23:13 UTCVendor advisory
  58. 2026-05-30 23:13 UTCGHSA enrichment
  59. 2026-05-29 13:40 UTCEPSS rescore
  60. 2026-05-28 13:42 UTCEPSS rescore
  61. 2026-05-28 13:42 UTCEPSS rescore
  62. 2026-05-28 13:42 UTCEPSS rescore
  63. 2026-05-27 13:38 UTCEPSS rescore
  64. 2026-05-27 13:37 UTCEPSS rescore
  65. 2026-05-27 13:37 UTCEPSS rescore
  66. 2026-05-26 23:43 UTCOSV refresh
  67. 2026-05-22 21:15 UTCEPSS rescore
  68. 2026-05-22 21:15 UTCEPSS rescore
  69. 2026-05-21 22:38 UTCEPSS rescore
  70. 2026-05-20 22:36 UTCEPSS rescore
  71. 2026-05-20 22:36 UTCEPSS rescore
  72. 2026-05-20 11:20 UTCEPSS rescore
  73. 2026-05-20 11:20 UTCEPSS rescore
  74. 2026-05-18 21:29 UTCEPSS rescore
  75. 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-31052✓ verified
    First seen Jan 22, 2008

    Apache 2.2.6 mod_negotiation - HTML Injection / HTTP Response Splitting

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2008-0455?
CVE-2008-0455 is a medium vulnerability published on January 25, 2008. Cross-site scripting (XSS) vulnerability in the mod_negotiation module in the Apache HTTP Server 2.2.6 and earlier in the 2.2.x series, 2.0.61 and earlier in the 2.0.x series, and 1.3.39 and earlier in the 1.3.x series allows remote authenticated users to inject arbitrary web script or HTML by…
When was CVE-2008-0455 disclosed?
CVE-2008-0455 was first published on January 25, 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-0455 actively exploited?
CVE-2008-0455 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 65% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-0455?
A fix for CVE-2008-0455 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2008-0455

Explore →

Is Your Infrastructure Affected by CVE-2008-0455?

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

Book a Demo →Browse All CVEs