CVE-2011-3192

HIGHCVSS v2 · 7.87.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.8 — v2 rates that HIGH (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:N/A:C. 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 98.9% 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
7.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 111 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 99%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 99%CVSS v2: 7.8Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 111

A fix is available — apply it.

The byterange filter in the Apache HTTP Server 1.3.x, 2.0.x through 2.0.64, and 2.2.x through 2.2.19 allows remote attackers to cause a denial of service (memory and CPU consumption) via a Range header that expresses multiple overlapping ranges, as exploited in the wild in August 2011, a different vulnerability than CVE-2007-0086.

Live · internet exposure

111 internet-exposed hosts are running an affected version of CVE-2011-3192 right now.

across 33 countries (United States, Japan, Spain, Canada, France)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)
7.8HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.8(low)
EG Risk
79(Track)
EG Risk 79/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
Severity78% × 45%
Exploitation99% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
99%
EPSS %ILE
100%
KEV
Not listed

Published

August 29, 2011

Last Modified

April 29, 2026

References (144)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2.2-bin (2.2.17-1ubuntu1.2) @ natty2026-05-29ubuntu
redhathttpd-0:2.2.17-13.2.ep5.el62011-09-21redhat
redhatpatch2011-09-21redhat
redhathttpd-0:2.0.46-78.ent2011-09-15redhat
redhathttpd-0:2.2.15-5.el6_0.12011-09-14redhat
redhathttpd-0:2.2.15-9.el6_1.22011-08-31redhat

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 rangeFixed inDependents
apache2—2.2.19-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.19-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.19-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.2.19-2—
Debian:5.0(1)
PackageVulnerable rangeFixed inDependents
apache22.2.9-10+lenny2 ... 2.2.9-10+lenny9 (8 versions)2.2.9-10+lenny10—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
apache22.2.16-6, 2.2.16-6+squeeze1, 2.2.16-6+squeeze1~bpo50+1, 2.2.16-6+squeeze2~bpo50+12.2.16-6+squeeze2—

Weakness Classification(1)

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

All Vendor Advisories

(6)

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 1× in last 7d / 3× 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-24 11:42 UTCOSV refresh
  2. 2026-08-08 16:31 UTCEPSS rescore
  3. 2026-08-08 07:49 UTCOSV refresh
  4. 2026-07-26 13:43 UTCEG score recompute▲ 7.80
  5. 2026-07-23 01:06 UTCVendor advisory
  6. 2026-07-23 01:06 UTCGHSA enrichment
  7. 2026-07-23 01:05 UTCEG score recompute▼ 9.00
  8. 2026-07-23 00:15 UTCOSV refresh
  9. 2026-07-23 00:09 UTCEG score recompute
  10. 2026-07-22 21:47 UTCEG score recompute
  11. 2026-07-22 14:03 UTCEPSS rescore
  12. 2026-07-11 08:22 UTCEPSS rescore
  13. 2026-07-11 08:22 UTCEPSS rescore
  14. 2026-07-05 18:59 UTCOSV refresh
  15. 2026-06-28 04:53 UTCEPSS rescore
  16. 2026-06-28 04:52 UTCEPSS rescore
  17. 2026-06-17 06:13 UTCOSV refresh
  18. 2026-06-15 17:44 UTCEPSS rescore
  19. 2026-06-13 22:57 UTCEPSS rescore
  20. 2026-06-13 22:57 UTCEPSS rescore
  21. 2026-06-12 23:08 UTCEPSS rescore
  22. 2026-06-10 22:14 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-08 14:14 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
Show 18 more
  1. 2026-06-05 06:08 UTCEPSS rescore
  2. 2026-06-05 06:07 UTCEPSS rescore
  3. 2026-06-04 13:09 UTCEPSS rescore
  4. 2026-06-04 13:09 UTCEPSS rescore
  5. 2026-05-29 07:09 UTCEG score recompute
  6. 2026-05-29 07:09 UTCVendor advisory
  7. 2026-05-29 07:09 UTCGHSA enrichment
  8. 2026-05-28 13:42 UTCEPSS rescore
  9. 2026-05-28 13:42 UTCEPSS rescore
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-27 13:38 UTCEPSS rescore
  12. 2026-05-27 13:38 UTCEPSS rescore
  13. 2026-05-22 21:15 UTCEPSS rescore
  14. 2026-05-22 21:15 UTCEPSS rescore
  15. 2026-05-22 21:15 UTCEPSS rescore
  16. 2026-05-22 16:13 UTCOSV refresh
  17. 2026-05-18 21:29 UTCEPSS rescore
  18. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(5 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCbluedragonsecurity/CVE-2011-3192-apache-exploit
    First seen May 14, 2026

    CVE-2011-3192 - Remote Apache DOS for Apache versions 1.3.x, 2.0.64 and below and 2.2.19 and below. Developed in 2011 by Antonius (ev1lut10n / w1sdom)

    Open source ↗
  • Exploit-DBEDB-18221
    First seen Dec 9, 2011

    Apache - Denial of Service

    Open source ↗
  • GitHub PoCtkisason/KillApachePy
    First seen Oct 26, 2011

    Python Apache Killer (Range Header DoS CVE-2011-3192)

    Open source ↗
  • Exploit-DBEDB-17696
    First seen Aug 19, 2011

    Apache - Remote Memory Exhaustion (Denial of Service)

    Open source ↗
  • Metasploitauxiliary/dos/http/apache_range_dos✓ verified
    First seen Aug 19, 2011

    Apache Range Header DoS (Apache Killer)

    Open source ↗

Frequently asked(4)

What is CVE-2011-3192?
CVE-2011-3192 is a high vulnerability published on August 29, 2011. The byterange filter in the Apache HTTP Server 1.3.x, 2.0.x through 2.0.64, and 2.2.x through 2.2.19 allows remote attackers to cause a denial of service (memory and CPU consumption) via a Range header that expresses multiple overlapping ranges, as exploited in the wild in August 2011, a different…
When was CVE-2011-3192 disclosed?
CVE-2011-3192 was first published in the National Vulnerability Database on August 29, 2011, 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-2011-3192 actively exploited?
CVE-2011-3192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
How do I remediate CVE-2011-3192?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-3192, 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-2011-3192

Explore →

Is Your Infrastructure Affected by CVE-2011-3192?

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

Start Free Scan →Browse All CVEs