CVE-2013-2070

MEDIUMCVSS v2 · 5.85.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.8 — 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:P/I:N/A:P. 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 11.9% 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
Elevated
5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 12%CVSS v2: 5.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

http/modules/ngx_http_proxy_module.c in nginx 1.1.4 through 1.2.8 and 1.3.0 through 1.4.0, when proxy_pass is used with untrusted HTTP servers, allows remote attackers to cause a denial of service (crash) and obtain sensitive information from worker process memory via a crafted proxy response, a similar vulnerability to CVE-2013-2028.

CVSS v2.0 (legacy)
5.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.8MEDIUMlow confidence
EG Risk
47
EG Risk 47/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)
Severity58% × 45%
The EG Score, 5.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). 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
12%
EPSS %ILE
96th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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: elevated) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). 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

Published

July 20, 2013

Last Modified

April 29, 2026

References (11)

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 1.4.1-1: fixed in 1.4.1-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 1.4.1-1: fixed in 1.4.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 1.4.1-1: fixed in 1.4.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nginx—
  • every version up to 1.4.1-1: fixed in 1.4.1-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
nginx1.2.1-2.2
  • every version up to 1.2.1-2.2+wheezy1: fixed in 1.2.1-2.2+wheezy1
—

Data Freshness Timeline

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

  1. 2026-10-11 13:39 UTCEPSS rescoreEPSS 12% · 96th percentile
  2. 2026-10-10 19:54 UTCEPSS rescoreEPSS 12% · 96th percentile
  3. 2026-10-09 20:00 UTCEPSS rescoreEPSS 12% · 96th percentile
  4. 2026-10-08 16:34 UTCEPSS rescoreEPSS 12% · 96th percentile
  5. 2026-10-07 23:39 UTCEPSS rescoreEPSS 12% · 96th percentile
  6. 2026-10-06 15:10 UTCEPSS rescoreEPSS 12% · 96th percentile
  7. 2026-10-05 17:38 UTCEPSS rescoreEPSS 12% · 96th percentile
  8. 2026-09-30 14:58 UTCEPSS rescoreEPSS 12% · 95th percentile
  9. 2026-09-30 07:28 UTCOSV refresh
  10. 2026-09-29 20:15 UTCEG score recompute
  11. 2026-09-27 13:39 UTCEPSS rescoreEPSS 12% · 95th percentile
  12. 2026-09-26 15:52 UTCEPSS rescoreEPSS 12% · 95th percentile
  13. 2026-09-24 13:57 UTCEPSS rescoreEPSS 12% · 95th percentile
  14. 2026-09-18 19:21 UTCEPSS rescoreEPSS 12% · 95th percentile
  15. 2026-09-15 03:04 UTCEPSS rescoreEPSS 12% · 95th percentile
  16. 2026-09-12 14:55 UTCEPSS rescoreEPSS 12% · 95th percentile
  17. 2026-09-11 13:23 UTCOSV refresh
  18. 2026-09-11 09:30 UTCEPSS rescoreEPSS 12% · 95th percentile
  19. 2026-09-07 15:56 UTCEPSS rescoreEPSS 12% · 95th percentile
  20. 2026-09-06 13:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  21. 2026-09-05 15:22 UTCEPSS rescoreEPSS 12% · 95th percentile
  22. 2026-09-04 13:55 UTCEPSS rescoreEPSS 12% · 95th percentile
  23. 2026-09-02 14:06 UTCEPSS rescoreEPSS 12% · 95th percentile
  24. 2026-09-01 13:47 UTCEPSS rescoreEPSS 12% · 95th percentile
  25. 2026-08-27 14:20 UTCEPSS rescoreEPSS 12% · 95th percentile
Show 63 more
  1. 2026-08-26 14:40 UTCEPSS rescoreEPSS 12% · 95th percentile
  2. 2026-08-25 13:43 UTCEPSS rescoreEPSS 12% · 95th percentile
  3. 2026-08-24 07:23 UTCEPSS rescoreEPSS 12% · 95th percentile
  4. 2026-08-23 18:52 UTCOSV refresh
  5. 2026-08-21 23:44 UTCEPSS rescoreEPSS 12% · 95th percentile
  6. 2026-08-20 22:50 UTCEPSS rescoreEPSS 12% · 95th percentile
  7. 2026-08-19 16:59 UTCEPSS rescoreEPSS 12% · 95th percentile
  8. 2026-08-18 13:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  9. 2026-08-16 02:09 UTCEPSS rescoreEPSS 12% · 95th percentile
  10. 2026-08-15 01:25 UTCEPSS rescoreEPSS 12% · 95th percentile
  11. 2026-08-12 13:45 UTCEPSS rescoreEPSS 12% · 95th percentile
  12. 2026-08-08 16:31 UTCEPSS rescoreEPSS 12% · 95th percentile
  13. 2026-08-07 18:49 UTCOSV refresh
  14. 2026-08-07 16:21 UTCEPSS rescoreEPSS 12% · 95th percentile
  15. 2026-08-06 13:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  16. 2026-08-05 19:12 UTCEPSS rescoreEPSS 12% · 95th percentile
  17. 2026-08-04 15:04 UTCEPSS rescoreEPSS 12% · 95th percentile
  18. 2026-08-02 02:22 UTCEPSS rescoreEPSS 12% · 95th percentile
  19. 2026-07-28 15:31 UTCEPSS rescoreEPSS 12% · 95th percentile
  20. 2026-07-26 13:47 UTCEG score recompute▲ 5.80
  21. 2026-07-25 14:12 UTCEPSS rescoreEPSS 12% · 95th percentile
  22. 2026-07-23 14:14 UTCEPSS rescoreEPSS 12% · 95th percentile
  23. 2026-07-23 01:09 UTCEG score recompute
  24. 2026-07-23 00:13 UTCEG score recompute
  25. 2026-07-22 21:51 UTCEG score recompute
  26. 2026-07-22 14:04 UTCEPSS rescoreEPSS 12% · 95th percentile
  27. 2026-07-22 11:37 UTCOSV refresh
  28. 2026-07-21 15:21 UTCEPSS rescoreEPSS 12% · 95th percentile
  29. 2026-07-20 17:03 UTCEPSS rescoreEPSS 12% · 95th percentile
  30. 2026-07-19 02:25 UTCEPSS rescoreEPSS 12% · 95th percentile
  31. 2026-07-18 10:00 UTCEPSS rescoreEPSS 12% · 95th percentile
  32. 2026-07-16 16:58 UTCEPSS rescoreEPSS 12% · 95th percentile
  33. 2026-07-15 16:54 UTCEPSS rescoreEPSS 12% · 95th percentile
  34. 2026-07-15 01:56 UTCEPSS rescoreEPSS 12% · 95th percentile
  35. 2026-07-13 22:26 UTCEPSS rescoreEPSS 12% · 95th percentile
  36. 2026-07-13 06:08 UTCEPSS rescoreEPSS 12% · 95th percentile
  37. 2026-07-11 08:23 UTCEPSS rescoreEPSS 12% · 95th percentile
  38. 2026-07-09 19:05 UTCEPSS rescoreEPSS 12% · 95th percentile
  39. 2026-07-08 15:10 UTCEPSS rescoreEPSS 12% · 95th percentile
  40. 2026-07-05 07:21 UTCOSV refresh
  41. 2026-07-05 02:26 UTCEPSS rescoreEPSS 12% · 95th percentile
  42. 2026-07-01 15:02 UTCEPSS rescoreEPSS 12% · 95th percentile
  43. 2026-06-30 23:19 UTCEPSS rescoreEPSS 12% · 95th percentile
  44. 2026-06-28 14:03 UTCEPSS rescoreEPSS 12% · 95th percentile
  45. 2026-06-28 04:53 UTCEPSS rescoreEPSS 12% · 95th percentile
  46. 2026-06-27 03:05 UTCEPSS rescoreEPSS 12% · 95th percentile
  47. 2026-06-25 13:46 UTCEPSS rescoreEPSS 12% · 95th percentile
  48. 2026-06-24 14:02 UTCEPSS rescoreEPSS 12% · 95th percentile
  49. 2026-06-23 21:30 UTCEPSS rescoreEPSS 12% · 95th percentile
  50. 2026-06-22 14:22 UTCEPSS rescoreEPSS 12% · 95th percentile
  51. 2026-06-21 14:53 UTCEPSS rescoreEPSS 12% · 95th percentile
  52. 2026-06-21 01:56 UTCEPSS rescoreEPSS 12% · 95th percentile
  53. 2026-06-18 17:49 UTCEPSS rescoreEPSS 12% · 95th percentile
  54. 2026-06-17 17:49 UTCEPSS rescoreEPSS 12% · 95th percentile
  55. 2026-06-16 18:14 UTCOSV refresh
  56. 2026-06-16 17:49 UTCEPSS rescoreEPSS 12% · 95th percentile
  57. 2026-06-15 17:44 UTCEPSS rescoreEPSS 12% · 95th percentile
  58. 2026-06-14 23:14 UTCEPSS rescoreEPSS 6.8% · 91st percentile
  59. 2026-06-13 22:57 UTCEPSS rescoreEPSS 6.8% · 91st percentile
  60. 2026-06-12 23:08 UTCEPSS rescoreEPSS 6.8% · 91st percentile
  61. 2026-06-11 13:56 UTCEPSS rescoreEPSS 6.8% · 91st percentile
  62. 2026-06-10 13:18 UTCEPSS rescoreEPSS 6.8% · 91st percentile
  63. 2026-06-08 14:14 UTCEPSS rescoreEPSS 6.8% · 91st percentile

Related CVEs(same product)

Frequently asked(4)

What is CVE-2013-2070?
CVE-2013-2070 is a medium-severity vulnerability; its CVE record was published on July 20, 2013. http/modules/ngxhttpproxymodule.c in nginx 1.1.4 through 1.2.8 and 1.3.0 through 1.4.0, when proxypass is used with untrusted HTTP servers, allows remote attackers to cause a denial of service (crash) and obtain sensitive information from worker process memory via a crafted proxy response, a…
When was CVE-2013-2070 made public?
CVE-2013-2070 was made public on May 7, 2013: 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 July 20, 2013. 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-2013-2070 actively exploited?
CVE-2013-2070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
How do I remediate CVE-2013-2070?
A fix for CVE-2013-2070 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-2013-2070

Explore →

Is Your Infrastructure Affected by CVE-2013-2070?

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

Book a Demo →Browse All CVEs