CVE-2012-4929

LOWCVSS v2 · 2.62.6
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 2.6 — v2 rates that LOW (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:H/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 4.3% 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
2.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS v2: 2.6Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The TLS protocol 1.2 and earlier, as used in Mozilla Firefox, Google Chrome, Qt, and other products, can encrypt compressed data without properly obfuscating the length of the unencrypted data, which allows man-in-the-middle attackers to obtain plaintext HTTP headers by observing length differences during a series of guesses in which a string in an HTTP request potentially matches an unknown string in an HTTP header, aka a "CRIME" attack.

CVSS v2.0 (legacy)
2.6LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
2.6(low)
EG Risk
32(Track)
EG Risk 32/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
Severity26% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
4%
EPSS %ILE
91%
KEV
Not listed

Published

September 15, 2012

Last Modified

April 29, 2026

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibqt4-network (4:4.7.4-0ubuntu8.2) @ oneiric2026-05-29ubuntu
ubuntuapache2.2-common (2.2.14-5ubuntu8.10) @ lucid2026-05-29ubuntu
ubuntulibssl1.0.0 (1.0.1c-4ubuntu8.1) @ raring2026-05-29ubuntu
redhatspice-client-msi-0:3.3-122014-04-17redhat
redhatrhev-hypervisor6-0:6.4-20130306.2.el6_42013-03-13redhat
redhatopenssl-0:1.0.0-27.el6_4.22013-03-04redhat

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

(26 across 7 ecosystems)
Debian:11(5)
PackageVulnerable rangeFixed inDependents
apache22.2.22-12
lighttpd1.4.30-1
nginx1.2.1-2.2
openssl1.0.1e-5
pound2.6-3
Debian:13(5)
PackageVulnerable rangeFixed inDependents
apache22.2.22-12
lighttpd1.4.30-1
nginx1.2.1-2.2
openssl1.0.1e-5
pound2.6-3
Debian:14(5)
PackageVulnerable rangeFixed inDependents
apache22.2.22-12
lighttpd1.4.30-1
nginx1.2.1-2.2
openssl1.0.1e-5
pound2.6-3
Debian:6.0(5)
PackageVulnerable rangeFixed inDependents
apache22.2.16-6 ... 2.2.16-6+squeeze8 (11 versions)2.2.16-6+squeeze10
lighttpd1.4.28-2, 1.4.28-2+squeeze1, 1.4.28-2+squeeze1.11.4.28-2+squeeze1.2
nginx0.7.67-3, 0.7.67-3+squeeze1, 0.7.67-3+squeeze20.7.67-3+squeeze3
openssl0.9.8o-4 ... 0.9.8o-4squeeze9 (15 versions)0.9.8o-4squeeze16
pound2.5-1, 2.5-1.1, 2.6-12.6-1+deb6u1
Debian:12(4)
PackageVulnerable rangeFixed inDependents
apache22.2.22-12
lighttpd1.4.30-1
nginx1.2.1-2.2
openssl1.0.1e-5
Debian:7(1)
PackageVulnerable rangeFixed inDependents
pound2.6-22.6-2+deb7u1
Debian:8(1)
PackageVulnerable rangeFixed inDependents
pound2.6-62.6-6+deb8u1

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 5× in last 7d / 17× 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.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-08-27 14:20 UTCEPSS rescore
  2. 2026-08-26 14:40 UTCEPSS rescore
  3. 2026-08-24 02:52 UTCOSV refresh
  4. 2026-08-23 00:12 UTCEPSS rescore
  5. 2026-08-21 23:43 UTCEPSS rescore
  6. 2026-08-19 16:59 UTCEPSS rescore
  7. 2026-08-18 13:42 UTCEPSS rescore
  8. 2026-08-16 02:09 UTCEPSS rescore
  9. 2026-08-15 01:25 UTCEPSS rescore
  10. 2026-08-09 13:42 UTCEPSS rescore
  11. 2026-08-08 16:31 UTCEPSS rescore
  12. 2026-08-08 00:19 UTCOSV refresh
  13. 2026-08-07 16:21 UTCEPSS rescore
  14. 2026-08-06 13:41 UTCEPSS rescore
  15. 2026-08-05 19:12 UTCEPSS rescore
  16. 2026-08-04 15:04 UTCEPSS rescore
  17. 2026-07-30 01:26 UTCEPSS rescore
  18. 2026-07-28 15:31 UTCEPSS rescore
  19. 2026-07-26 13:46 UTCEG score recompute 2.60
  20. 2026-07-25 14:12 UTCEPSS rescore
  21. 2026-07-23 14:14 UTCEPSS rescore
  22. 2026-07-23 01:08 UTCEG score recompute
  23. 2026-07-23 00:11 UTCEG score recompute
  24. 2026-07-22 21:50 UTCEG score recompute
  25. 2026-07-22 17:20 UTCOSV refresh
Show 75 more
  1. 2026-07-22 14:04 UTCEPSS rescore
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-21 15:21 UTCEPSS rescore
  4. 2026-07-20 17:03 UTCEPSS rescore
  5. 2026-07-20 17:03 UTCEPSS rescore
  6. 2026-07-19 14:27 UTCEPSS rescore
  7. 2026-07-19 02:25 UTCEPSS rescore
  8. 2026-07-18 10:00 UTCEPSS rescore
  9. 2026-07-16 16:58 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-15 01:56 UTCEPSS rescore
  13. 2026-07-13 22:25 UTCEPSS rescore
  14. 2026-07-13 06:08 UTCEPSS rescore
  15. 2026-07-11 08:22 UTCEPSS rescore
  16. 2026-07-09 19:05 UTCEPSS rescore
  17. 2026-07-08 15:10 UTCEPSS rescore
  18. 2026-07-08 15:10 UTCEPSS rescore
  19. 2026-07-06 16:23 UTCEPSS rescore
  20. 2026-07-06 02:19 UTCEPSS rescore
  21. 2026-07-06 02:19 UTCEPSS rescore
  22. 2026-07-05 12:29 UTCOSV refresh
  23. 2026-07-05 02:26 UTCEPSS rescore
  24. 2026-07-04 06:27 UTCEPSS rescore
  25. 2026-07-02 14:01 UTCEPSS rescore
  26. 2026-07-01 15:02 UTCEPSS rescore
  27. 2026-06-30 23:19 UTCEPSS rescore
  28. 2026-06-30 23:19 UTCEPSS rescore
  29. 2026-06-29 14:02 UTCEPSS rescore
  30. 2026-06-28 14:03 UTCEPSS rescore
  31. 2026-06-28 04:53 UTCEPSS rescore
  32. 2026-06-28 04:53 UTCEPSS rescore
  33. 2026-06-27 03:05 UTCEPSS rescore
  34. 2026-06-27 03:05 UTCEPSS rescore
  35. 2026-06-25 13:46 UTCEPSS rescore
  36. 2026-06-25 13:46 UTCEPSS rescore
  37. 2026-06-24 14:02 UTCEPSS rescore
  38. 2026-06-24 14:02 UTCEPSS rescore
  39. 2026-06-23 21:30 UTCEPSS rescore
  40. 2026-06-22 14:22 UTCEPSS rescore
  41. 2026-06-22 14:22 UTCEPSS rescore
  42. 2026-06-21 14:53 UTCEPSS rescore
  43. 2026-06-21 01:56 UTCEPSS rescore
  44. 2026-06-21 01:56 UTCEPSS rescore
  45. 2026-06-19 19:22 UTCEPSS rescore
  46. 2026-06-19 19:22 UTCEPSS rescore
  47. 2026-06-18 17:49 UTCEPSS rescore
  48. 2026-06-18 17:49 UTCEPSS rescore
  49. 2026-06-17 17:49 UTCEPSS rescore
  50. 2026-06-17 17:49 UTCEPSS rescore
  51. 2026-06-16 23:35 UTCOSV refresh
  52. 2026-06-16 17:49 UTCEPSS rescore
  53. 2026-06-16 17:49 UTCEPSS rescore
  54. 2026-06-15 17:44 UTCEPSS rescore
  55. 2026-06-14 23:14 UTCEPSS rescore
  56. 2026-06-14 23:14 UTCEPSS rescore
  57. 2026-06-13 22:57 UTCEPSS rescore
  58. 2026-06-12 23:08 UTCEPSS rescore
  59. 2026-06-11 13:56 UTCEPSS rescore
  60. 2026-06-10 22:14 UTCEPSS rescore
  61. 2026-06-10 13:18 UTCEPSS rescore
  62. 2026-06-08 14:14 UTCEPSS rescore
  63. 2026-06-08 14:14 UTCEPSS rescore
  64. 2026-06-07 15:22 UTCEPSS rescore
  65. 2026-06-07 15:22 UTCEPSS rescore
  66. 2026-06-06 13:45 UTCEPSS rescore
  67. 2026-06-06 13:45 UTCEPSS rescore
  68. 2026-06-05 22:44 UTCEPSS rescore
  69. 2026-06-05 22:44 UTCEPSS rescore
  70. 2026-06-05 06:08 UTCEPSS rescore
  71. 2026-06-05 06:08 UTCEPSS rescore
  72. 2026-06-04 13:09 UTCEPSS rescore
  73. 2026-06-02 20:10 UTCEPSS rescore
  74. 2026-06-02 20:10 UTCEPSS rescore
  75. 2026-06-01 13:49 UTCEPSS rescore

Publicly available exploits

(2 references)

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

  • GitHub PoCanthophilee/A2SV--SSL-VUL-Scan
    First seen Jan 1, 2021

    A2SV = Auto Scanning to SSL Vulnerability HeartBleed, CCS Injection, SSLv3 POODLE, FREAK... etc Support Vulnerability [CVE-2007-1858] Anonymous Cipher [CVE-2012-4929] CRIME(SPDY) [CVE-2014-0160] CCS Injection [CVE-2014-0224] HeartBleed [CVE-2014-3566] SSLv3 POODLE [CVE-2015-0204] FREAK Attack [CVE-2015-4000] LOGJAM Attack [CVE-2016-0800] SSLv2 DROWN Installation : $ apt update && apt upgrade $ apt install git $ apt install python2 $ apt install python $ git clone https://github.com/hahwul/ a2sv $ cd a2sv $ chmod +x * $ pip2 install -r requirements.txt usage : $ python2 a2sv.py -h It shows all commands how we can use this tool $ python a2sv.py -t 127.0.0.1 127.0.0.1 = target means here own device

    Open source ↗
  • GitHub PoCmpgn/CRIME-poc
    First seen Apr 21, 2018

    :hocho: CRIME attack PoC : a compression oracle attacks CVE-2012-4929 :hocho:

    Open source ↗

Frequently asked(4)

What is CVE-2012-4929?
CVE-2012-4929 is a low vulnerability published on September 15, 2012. The TLS protocol 1.2 and earlier, as used in Mozilla Firefox, Google Chrome, Qt, and other products, can encrypt compressed data without properly obfuscating the length of the unencrypted data, which allows man-in-the-middle attackers to obtain plaintext HTTP headers by observing length differences…
When was CVE-2012-4929 disclosed?
CVE-2012-4929 was first published in the National Vulnerability Database on September 15, 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-4929 actively exploited?
CVE-2012-4929 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 9.5% of all scored CVEs.
How do I remediate CVE-2012-4929?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-4929, 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-2012-4929

Explore →

Is Your Infrastructure Affected by CVE-2012-4929?

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