CVE-2012-0053

MEDIUMCVSS v2 · 4.34.3
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 4.3 — 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:M/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 82% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized
4.3EG
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).
  • 96 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 82%
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 82%CVSS v2: 4.3Exploit: Exploit-DB (verified)Exposed services: 96

A fix is available — apply it.

protocol.c in the Apache HTTP Server 2.2.x through 2.2.21 does not properly restrict header information during construction of Bad Request (aka 400) error documents, which allows remote attackers to obtain the values of HTTPOnly cookies via vectors involving a (1) long or (2) malformed header in conjunction with crafted web script.

Internet exposure · derived from Shodan data

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

across 27 countries (United States, Japan, Canada, Germany, France)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
52
EG Risk 52/100

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 (value × EchelonGraph’s weight)
Severity43% × 45%
The EG Score, 4.3 of 10.
Exploitation82% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
82%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and 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 (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

January 28, 2012

Last Modified

April 29, 2026

References (45)

15 of 45 shown · show the other 30

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuapache2.2-common (2.2.17-1ubuntu1.5) @ natty2026-05-29ubuntu
redhatpatch2012-05-07redhat
redhathttpd-0:2.2.17-15.4.ep5.el62012-05-07redhat
redhathttpd-0:2.2.3-63.el5_8.12012-02-21redhat
redhathttpd-0:2.2.15-15.el6_2.12012-02-13redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-1: fixed in 2.2.22-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-1: fixed in 2.2.22-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-1: fixed in 2.2.22-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.2.22-1: fixed in 2.2.22-1
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.2.9-10+lenny10 ... 2.2.9-10+lenny9 (10 versions)
  • every version up to 2.2.9-10+lenny12: fixed in 2.2.9-10+lenny12
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.2.16-6 ... 2.2.16-6+squeeze4~bpo50+1 (8 versions)
  • every version up to 2.2.16-6+squeeze6: fixed in 2.2.16-6+squeeze6
—

All Vendor Advisories

(5)

Data Freshness Timeline

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

  1. 2026-10-12 01:40 UTCEG score recompute
  2. 2026-10-10 19:54 UTCEPSS rescoreEPSS 82% · 99th percentile
  3. 2026-10-07 23:39 UTCEPSS rescoreEPSS 82% · 99th percentile
  4. 2026-10-05 17:37 UTCEPSS rescoreEPSS 82% · 99th percentile
  5. 2026-09-30 20:10 UTCOSV refresh
  6. 2026-09-29 08:25 UTCEG score recompute
  7. 2026-09-28 13:44 UTCEPSS rescoreEPSS 82% · 99th percentile
  8. 2026-09-24 13:57 UTCEPSS rescoreEPSS 82% · 99th percentile
  9. 2026-09-16 13:58 UTCEPSS rescoreEPSS 82% · 99th percentile
  10. 2026-09-15 03:04 UTCEPSS rescoreEPSS 82% · 99th percentile
  11. 2026-09-12 02:40 UTCOSV refresh
  12. 2026-09-05 15:22 UTCEPSS rescoreEPSS 83% · 99th percentile
  13. 2026-08-28 21:34 UTCEPSS rescoreEPSS 83% · 99th percentile
  14. 2026-08-26 14:40 UTCEPSS rescoreEPSS 83% · 99th percentile
  15. 2026-08-24 08:27 UTCOSV refresh
  16. 2026-08-21 23:43 UTCEPSS rescoreEPSS 83% · 99th percentile
  17. 2026-08-19 16:59 UTCEPSS rescoreEPSS 83% · 99th percentile
  18. 2026-08-16 02:09 UTCEPSS rescoreEPSS 83% · 99th percentile
  19. 2026-08-15 01:25 UTCEPSS rescoreEPSS 83% · 99th percentile
  20. 2026-08-09 13:42 UTCEPSS rescoreEPSS 83% · 99th percentile
  21. 2026-08-08 16:31 UTCEPSS rescoreEPSS 83% · 99th percentile
  22. 2026-08-08 04:49 UTCOSV refresh
  23. 2026-08-07 16:21 UTCEPSS rescoreEPSS 83% · 99th percentile
  24. 2026-08-05 19:12 UTCEPSS rescoreEPSS 83% · 99th percentile
  25. 2026-07-28 15:31 UTCEPSS rescoreEPSS 83% · 99th percentile
Show 51 more
  1. 2026-07-26 13:44 UTCEG score recomputeAssessed again: 4.3 MEDIUM
  2. 2026-07-23 01:06 UTCEG score recompute▼ 8.60
  3. 2026-07-23 00:10 UTCEG score recomputeFirst assessed: 8.6 HIGH
  4. 2026-07-22 21:54 UTCOSV refresh
  5. 2026-07-22 21:48 UTCEG score recompute
  6. 2026-07-22 14:04 UTCEPSS rescoreEPSS 83% · 99th percentile
  7. 2026-07-21 15:21 UTCEPSS rescoreEPSS 83% · 99th percentile
  8. 2026-07-20 17:03 UTCEPSS rescoreEPSS 83% · 99th percentile
  9. 2026-07-15 16:54 UTCEPSS rescoreEPSS 83% · 99th percentile
  10. 2026-07-15 01:56 UTCEPSS rescoreEPSS 83% · 99th percentile
  11. 2026-07-13 06:08 UTCEPSS rescoreEPSS 83% · 99th percentile
  12. 2026-07-09 19:05 UTCEPSS rescoreEPSS 83% · 99th percentile
  13. 2026-07-05 16:59 UTCOSV refresh
  14. 2026-07-04 06:27 UTCEPSS rescoreEPSS 83% · 99th percentile
  15. 2026-07-01 15:02 UTCEPSS rescoreEPSS 83% · 99th percentile
  16. 2026-06-27 03:05 UTCEPSS rescoreEPSS 83% · 99th percentile
  17. 2026-06-24 14:02 UTCEPSS rescoreEPSS 83% · 99th percentile
  18. 2026-06-23 21:30 UTCEPSS rescoreEPSS 83% · 99th percentile
  19. 2026-06-21 14:53 UTCEPSS rescoreEPSS 83% · 99th percentile
  20. 2026-06-21 01:56 UTCEPSS rescoreEPSS 83% · 99th percentile
  21. 2026-06-17 04:05 UTCOSV refresh
  22. 2026-06-16 17:49 UTCEPSS rescoreEPSS 83% · 99th percentile
  23. 2026-06-15 17:44 UTCEPSS rescoreEPSS 83% · 99th percentile
  24. 2026-06-14 23:14 UTCEPSS rescoreEPSS 24% · 96th percentile
  25. 2026-06-13 22:57 UTCEPSS rescoreEPSS 24% · 96th percentile
  26. 2026-06-12 23:08 UTCEPSS rescoreEPSS 24% · 96th percentile
  27. 2026-06-11 13:56 UTCEPSS rescoreEPSS 24% · 96th percentile
  28. 2026-06-10 22:14 UTCEPSS rescoreEPSS 24% · 96th percentile
  29. 2026-06-10 13:18 UTCEPSS rescoreEPSS 24% · 96th percentile
  30. 2026-06-08 14:14 UTCEPSS rescoreEPSS 24% · 96th percentile
  31. 2026-06-07 15:22 UTCEPSS rescoreEPSS 34% · 97th percentile
  32. 2026-06-06 13:45 UTCEPSS rescoreEPSS 34% · 97th percentile
  33. 2026-06-05 22:44 UTCEPSS rescoreEPSS 34% · 97th percentile
  34. 2026-06-05 06:08 UTCEPSS rescoreEPSS 34% · 97th percentile
  35. 2026-06-04 13:09 UTCEPSS rescoreEPSS 34% · 97th percentile
  36. 2026-06-02 20:10 UTCEPSS rescoreEPSS 34% · 97th percentile
  37. 2026-05-31 22:28 UTCEPSS rescoreEPSS 34% · 97th percentile
  38. 2026-05-31 00:14 UTCEPSS rescoreEPSS 34% · 97th percentile
  39. 2026-05-29 13:41 UTCEPSS rescoreEPSS 34% · 97th percentile
  40. 2026-05-29 05:37 UTCEG score recompute
  41. 2026-05-29 05:37 UTCVendor advisory
  42. 2026-05-29 05:37 UTCGHSA enrichmentGHSA-x2wg-fp56-xx79
  43. 2026-05-28 13:42 UTCEPSS rescoreEPSS 34% · 97th percentile
  44. 2026-05-27 13:38 UTCEPSS rescoreEPSS 34% · 97th percentile
  45. 2026-05-26 13:41 UTCEPSS rescoreEPSS 34% · 97th percentile
  46. 2026-05-26 07:16 UTCEPSS rescoreEPSS 34% · 97th percentile
  47. 2026-05-24 16:43 UTCEPSS rescoreEPSS 34% · 97th percentile
  48. 2026-05-22 21:15 UTCEPSS rescoreEPSS 34% · 97th percentile
  49. 2026-05-22 01:06 UTCOSV refresh
  50. 2026-05-21 22:39 UTCEPSS rescoreEPSS 34% · 97th percentile
  51. 2026-05-20 22:37 UTCEPSS rescoreEPSS 34% · 97th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-18442✓ verified
    Published Jan 31, 2012

    Apache - httpOnly Cookie Disclosure

    Open source ↗

Frequently asked(4)

What is CVE-2012-0053?
CVE-2012-0053 is a medium-severity vulnerability; its CVE record was published on January 28, 2012. protocol.c in the Apache HTTP Server 2.2.x through 2.2.21 does not properly restrict header information during construction of Bad Request (aka 400) error documents, which allows remote attackers to obtain the values of HTTPOnly cookies via vectors involving a (1) long or (2) malformed header in…
When was CVE-2012-0053 made public?
CVE-2012-0053 was made public on January 23, 2012: 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 January 28, 2012. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2012-0053 actively exploited?
CVE-2012-0053 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 82% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2012-0053?
A fix for CVE-2012-0053 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-2012-0053

Explore →

Is Your Infrastructure Affected by CVE-2012-0053?

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