CVE-2013-5704

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: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 60.2% 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
Elevated
5.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 388 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 60%
CISA-KEV: Not listedEPSS PROB: 60%CVSS v2: 5.0Exploit: Elevated riskExposed: 388

A fix is available — apply it.

The mod_headers module in the Apache HTTP Server 2.2.22 allows remote attackers to bypass "RequestHeader unset" directives by placing a header in the trailer portion of data sent with chunked transfer coding. NOTE: the vendor states "this is not a security issue in httpd as such."

Live · internet exposure

388 internet-exposed hosts are running an affected version of CVE-2013-5704 right now.

across 56 countries (United States, Japan, Germany, France, United Kingdom)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 v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0(low)
EG Risk
51(Track)
EG Risk 51/100SSVC: Track

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%
Exploitation60% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
60%
EPSS %ILE
99%
KEV
Not listed

Published

April 15, 2014

Last Modified

May 6, 2026

References (94)

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2.2-bin (2.4.10-1ubuntu1.1) @ utopic2026-05-28ubuntu
redhatmod_cluster-native-0:1.2.9-6.Final_redhat_2.ep6.el72016-01-21redhat
redhathttpd2016-01-21redhat
redhatpatch2015-12-16redhat
redhattomcat-vault-0:1.0.8-4.Final_redhat_4.1.ep7.el62015-12-16redhat
redhattomcat-vault-0:1.0.8-4.Final_redhat_4.1.ep7.el72015-12-16redhat
redhathttpd-0:2.2.15-45.el62015-07-20redhat
redhathttpd-0:2.4.6-31.el72015-03-05redhat
redhathttpd24-httpd-0:2.4.6-25.el72014-12-09redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-2—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
apache22.2.16-6 ... 2.2.16-6+squeeze8 (15 versions)2.2.16-6+squeeze14—

All Vendor Advisories

(9)

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

Frequently asked(4)

What is CVE-2013-5704?
CVE-2013-5704 is a medium vulnerability published on April 15, 2014. The mod_headers module in the Apache HTTP Server 2.2.22 allows remote attackers to bypass "RequestHeader unset" directives by placing a header in the trailer portion of data sent with chunked transfer coding. NOTE: the vendor states "this is not a security issue in httpd as such."
When was CVE-2013-5704 disclosed?
CVE-2013-5704 was first published in the National Vulnerability Database on April 15, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-5704 actively exploited?
CVE-2013-5704 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60% probability of exploitation in the next 30 days, which ranks it in the top 0.9% of all scored CVEs.
How do I remediate CVE-2013-5704?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-5704, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-5704

Explore →

Is Your Infrastructure Affected by CVE-2013-5704?

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

Start Free Scan →Browse All CVEs