CVE-2012-4929

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 4%CVSS: Exploit: NoneExposed: 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 v3
EG Score
0.0(none)
EPSS
89.9%
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.

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 10× in last 7d / 45× 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-06 16:23 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 12:29 UTCOSV refresh
  5. 2026-07-05 02:26 UTCEPSS rescore
  6. 2026-07-04 06:27 UTCEPSS rescore
  7. 2026-07-02 14:01 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-28 14:03 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-28 04:53 UTCEPSS rescore
  15. 2026-06-27 03:05 UTCEPSS rescore
  16. 2026-06-27 03:05 UTCEPSS rescore
  17. 2026-06-25 13:46 UTCEPSS rescore
  18. 2026-06-25 13:46 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-24 14:02 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:22 UTCEPSS rescore
  23. 2026-06-22 14:22 UTCEPSS rescore
  24. 2026-06-21 14:53 UTCEPSS rescore
  25. 2026-06-21 01:56 UTCEPSS rescore
Show 60 more
  1. 2026-06-21 01:56 UTCEPSS rescore
  2. 2026-06-19 19:22 UTCEPSS rescore
  3. 2026-06-19 19:22 UTCEPSS rescore
  4. 2026-06-18 17:49 UTCEPSS rescore
  5. 2026-06-18 17:49 UTCEPSS rescore
  6. 2026-06-17 17:49 UTCEPSS rescore
  7. 2026-06-17 17:49 UTCEPSS rescore
  8. 2026-06-16 23:35 UTCOSV refresh
  9. 2026-06-16 17:49 UTCEPSS rescore
  10. 2026-06-16 17:49 UTCEPSS rescore
  11. 2026-06-15 17:44 UTCEPSS rescore
  12. 2026-06-14 23:14 UTCEPSS rescore
  13. 2026-06-14 23:14 UTCEPSS rescore
  14. 2026-06-13 22:57 UTCEPSS rescore
  15. 2026-06-12 23:08 UTCEPSS rescore
  16. 2026-06-11 13:56 UTCEPSS rescore
  17. 2026-06-10 22:14 UTCEPSS rescore
  18. 2026-06-10 13:18 UTCEPSS rescore
  19. 2026-06-08 14:14 UTCEPSS rescore
  20. 2026-06-08 14:14 UTCEPSS rescore
  21. 2026-06-07 15:22 UTCEPSS rescore
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 22:44 UTCEPSS rescore
  26. 2026-06-05 22:44 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-06-04 13:09 UTCEPSS rescore
  30. 2026-06-02 20:10 UTCEPSS rescore
  31. 2026-06-02 20:10 UTCEPSS rescore
  32. 2026-06-01 13:49 UTCEPSS rescore
  33. 2026-05-31 22:28 UTCEPSS rescore
  34. 2026-05-31 22:28 UTCEPSS rescore
  35. 2026-05-31 00:14 UTCEPSS rescore
  36. 2026-05-31 00:14 UTCEPSS rescore
  37. 2026-05-29 13:41 UTCEPSS rescore
  38. 2026-05-29 02:45 UTCEG score recompute
  39. 2026-05-29 02:45 UTCVendor advisory
  40. 2026-05-29 02:44 UTCGHSA enrichment
  41. 2026-05-28 13:42 UTCEPSS rescore
  42. 2026-05-28 13:42 UTCEPSS rescore
  43. 2026-05-27 20:35 UTCOSV refresh
  44. 2026-05-27 13:38 UTCEPSS rescore
  45. 2026-05-27 13:38 UTCEPSS rescore
  46. 2026-05-26 13:41 UTCEPSS rescore
  47. 2026-05-26 13:41 UTCEPSS rescore
  48. 2026-05-24 16:43 UTCEPSS rescore
  49. 2026-05-22 21:15 UTCEPSS rescore
  50. 2026-05-22 21:15 UTCEPSS rescore
  51. 2026-05-22 21:15 UTCEPSS rescore
  52. 2026-05-21 22:39 UTCEPSS rescore
  53. 2026-05-20 22:37 UTCEPSS rescore
  54. 2026-05-20 22:37 UTCEPSS rescore
  55. 2026-05-20 22:37 UTCEPSS rescore
  56. 2026-05-20 11:21 UTCEPSS rescore
  57. 2026-05-20 11:21 UTCEPSS rescore
  58. 2026-05-20 11:21 UTCEPSS rescore
  59. 2026-05-18 21:29 UTCEPSS rescore
  60. 2026-05-18 21:29 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 none 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 89.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

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