CVE-2012-0053

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 27 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS: 83%CVSS: —Exploit: NoneExposed: 27

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.

Live · internet exposure

27 internet-exposed hosts are running an affected version of CVE-2012-0053 right now.

across 13 countries (United States, Japan, Germany, Denmark, Hungary)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
—
EG Score
0.0(none)
EPSS
99.6%
KEV
Not listed

Published

January 28, 2012

Last Modified

April 29, 2026

References (90)

Patch Availability(5)

Vendor / EcosystemFixed in / 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.

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 3× in last 7d / 24× 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-07-05 16:59 UTCOSV refresh
  2. 2026-07-04 06:27 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-06-27 03:05 UTCEPSS rescore
  5. 2026-06-27 03:05 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-24 14:02 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-21 14:53 UTCEPSS rescore
  10. 2026-06-21 01:56 UTCEPSS rescore
  11. 2026-06-21 01:56 UTCEPSS rescore
  12. 2026-06-17 04:05 UTCOSV refresh
  13. 2026-06-16 17:49 UTCEPSS rescore
  14. 2026-06-16 17:49 UTCEPSS rescore
  15. 2026-06-15 17:44 UTCEPSS rescore
  16. 2026-06-14 23:14 UTCEPSS rescore
  17. 2026-06-14 23:14 UTCEPSS rescore
  18. 2026-06-13 22:57 UTCEPSS rescore
  19. 2026-06-12 23:08 UTCEPSS rescore
  20. 2026-06-11 13:56 UTCEPSS rescore
  21. 2026-06-10 22:14 UTCEPSS rescore
  22. 2026-06-10 13:18 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
Show 41 more
  1. 2026-06-07 15:22 UTCEPSS rescore
  2. 2026-06-06 13:45 UTCEPSS rescore
  3. 2026-06-06 13:45 UTCEPSS rescore
  4. 2026-06-05 22:44 UTCEPSS rescore
  5. 2026-06-05 22:44 UTCEPSS rescore
  6. 2026-06-05 06:08 UTCEPSS rescore
  7. 2026-06-05 06:08 UTCEPSS rescore
  8. 2026-06-04 13:09 UTCEPSS rescore
  9. 2026-06-02 20:10 UTCEPSS rescore
  10. 2026-06-02 20:10 UTCEPSS rescore
  11. 2026-05-31 22:28 UTCEPSS rescore
  12. 2026-05-31 22:28 UTCEPSS rescore
  13. 2026-05-31 00:14 UTCEPSS rescore
  14. 2026-05-31 00:14 UTCEPSS rescore
  15. 2026-05-29 13:41 UTCEPSS rescore
  16. 2026-05-29 05:37 UTCEG score recompute
  17. 2026-05-29 05:37 UTCVendor advisory
  18. 2026-05-29 05:37 UTCGHSA enrichment
  19. 2026-05-28 13:42 UTCEPSS rescore
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-27 13:38 UTCEPSS rescore
  22. 2026-05-27 13:38 UTCEPSS rescore
  23. 2026-05-26 13:41 UTCEPSS rescore
  24. 2026-05-26 13:41 UTCEPSS rescore
  25. 2026-05-26 07:16 UTCEPSS rescore
  26. 2026-05-26 07:16 UTCEPSS rescore
  27. 2026-05-26 07:16 UTCEPSS rescore
  28. 2026-05-24 16:43 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-22 21:15 UTCEPSS rescore
  31. 2026-05-22 21:15 UTCEPSS rescore
  32. 2026-05-22 01:06 UTCOSV refresh
  33. 2026-05-21 22:39 UTCEPSS rescore
  34. 2026-05-20 22:37 UTCEPSS rescore
  35. 2026-05-20 22:37 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 11:21 UTCEPSS rescore
  38. 2026-05-20 11:21 UTCEPSS rescore
  39. 2026-05-20 11:21 UTCEPSS rescore
  40. 2026-05-18 21:29 UTCEPSS rescore
  41. 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-18442✓ verified
    First seen Jan 31, 2012

    Apache - httpOnly Cookie Disclosure

    Open source ↗

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2012-0053?
CVE-2012-0053 is a none vulnerability 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 disclosed?
CVE-2012-0053 was first published in the National Vulnerability Database on January 28, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-0053 actively exploited?
CVE-2012-0053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2012-0053?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-0053, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs