CVE-2012-4929: The TLS protocol 1.2 and earlier, as used in Mozilla Firefox, Google Chrome, Qt, and other products, can encrypt compressed data without…
Noroxi assessment
Priority: Monitor (action score 11/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.3% (FIRST EPSS); higher than 91.3% of all records.
- Special conditions such as timing or configuration are required.
- Fixed version: apache2 (Debian:12) 2.2.22-12; lighttpd (Debian:12) 1.4.30-1; nginx (Debian:12) 1.2.1-2.2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to apache2 (Debian:12) 2.2.22-12; lighttpd (Debian:12) 1.4.30-1; nginx (Debian:12) 1.2.1-2.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 15, 2012
- Updated
- Jun 16, 2026
- EPSS
- 4.3% · 91th percentile
- CWE
- CWE-310
Report tools
Action score
11
Low priority for now.
- CVSS
- 10 / 40 · 2.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| chrome | cpe:2.3:a:google:chrome | |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| mozilla | firefox | cpe:2.3:a:mozilla:firefox |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux7.0
- debian debian linux8.0
- google chromeall versions
- mozilla firefoxall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | apache2 | before 2.2.22-12 | 2.2.22-12 |
| Debian:12 | lighttpd | before 1.4.30-1 | 1.4.30-1 |
| Debian:12 | nginx | before 1.2.1-2.2 | 1.2.1-2.2 |
| Debian:12 | openssl | before 1.0.1e-5 | 1.0.1e-5 |
| Debian:13 | pound | before 2.6-3 | 2.6-3 |
| Debian:6.0 | apache2 | before 2.2.16-6+squeeze10 | 2.2.16-6+squeeze10 |
| Debian:6.0 | lighttpd | before 1.4.28-2+squeeze1.2 | 1.4.28-2+squeeze1.2 |
| Debian:6.0 | nginx | before 0.7.67-3+squeeze3 | 0.7.67-3+squeeze3 |
| Debian:6.0 | openssl | before 0.9.8o-4squeeze16 | 0.9.8o-4squeeze16 |
| Debian:6.0 | pound | before 2.6-1+deb6u1 | 2.6-1+deb6u1 |
| Debian:7 | pound | before 2.6-2+deb7u1 | 2.6-2+deb7u1 |
| Debian:8 | pound | before 2.6-6+deb8u1 | 2.6-6+deb8u1 |
| openSUSE:Tumbleweed | links | before 2.13-1.3 | 2.13-1.3 |
| openSUSE:Tumbleweed | lynx | before 2.8.8rel.2-4.13 | 2.8.8rel.2-4.13 |
| openSUSE:Tumbleweed | w3m | before 0.5.3.git20161120-1.1 | 0.5.3.git20161120-1.1 |
| openSUSE:Tumbleweed | wget | before 1.18-2.3 | 1.18-2.3 |
| Red Hat:enterprise_linux:5::server | openssl | before 0:0.9.8e-26.el5_9.1 | 0:0.9.8e-26.el5_9.1 |
| Red Hat:enterprise_linux:5::server | openssl-debuginfo | before 0:0.9.8e-26.el5_9.1 | 0:0.9.8e-26.el5_9.1 |
| Red Hat:enterprise_linux:5::server | openssl-devel | before 0:0.9.8e-26.el5_9.1 | 0:0.9.8e-26.el5_9.1 |
| Red Hat:enterprise_linux:5::server | openssl-perl | before 0:0.9.8e-26.el5_9.1 | 0:0.9.8e-26.el5_9.1 |
| Red Hat:enterprise_linux:6::client | openssl | before 0:1.0.0-27.el6_4.2 | 0:1.0.0-27.el6_4.2 |
| Red Hat:enterprise_linux:6::client | openssl-debuginfo | before 0:1.0.0-27.el6_4.2 | 0:1.0.0-27.el6_4.2 |
| Red Hat:enterprise_linux:6::client | openssl-devel | before 0:1.0.0-27.el6_4.2 | 0:1.0.0-27.el6_4.2 |
| Red Hat:enterprise_linux:6::client | openssl-perl | before 0:1.0.0-27.el6_4.2 | 0:1.0.0-27.el6_4.2 |
+7
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV95Now
- CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV90Now
- CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2012-4908Sep 13, 2012 · Google Chrome before 18.0.1025308 on Android allows remote attackers to bypass the Same Origin Policy and obtain access to local files via…31Monitor
- ← EarlierCVE-2012-4909Sep 13, 2012 · Google Chrome before 18.0.1025308 on Android allows remote attackers to obtain cookie information via a crafted application.18Monitor
- Later →CVE-2012-4930Sep 15, 2012 · The SPDY protocol 3 and earlier, as used in Mozilla Firefox, Google Chrome, and other products, can perform TLS encryption of compressed…11Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:apache2 | 2.2.22-12 · Debian:12 | Package registry (OSV) |
| debian:lighttpd | 1.4.30-1 · Debian:12 | Package registry (OSV) |
| debian:nginx | 1.2.1-2.2 · Debian:12 | Package registry (OSV) |
| debian:openssl | 1.0.1e-5 · Debian:12 | Package registry (OSV) |
| debian:pound | 2.6-3 · Debian:13 | Package registry (OSV) |
| opensuse:links | 2.13-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:lynx | 2.8.8rel.2-4.13 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:w3m | 0.5.3.git20161120-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:wget | 1.18-2.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:openssl | 0:0.9.8e-26.el5_9.1 · Red Hat:enterprise_linux:5::server | Package registry (OSV) |
| red hat:openssl-debuginfo | 0:0.9.8e-26.el5_9.1 · Red Hat:enterprise_linux:5::server | Package registry (OSV) |
| red hat:openssl-devel | 0:0.9.8e-26.el5_9.1 · Red Hat:enterprise_linux:5::server | Package registry (OSV) |
| red hat:openssl-perl | 0:0.9.8e-26.el5_9.1 · Red Hat:enterprise_linux:5::server | Package registry (OSV) |
| red hat:openssl-static | 0:1.0.0-27.el6_4.2 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:rhev-hypervisor6 | 0:6.4-20130306.2.el6_4 · Red Hat:enterprise_linux:6::hypervisor | Package registry (OSV) |
| red hat:rhevm-spice-client | 0:3.3-12.el6_5 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x64-cab | 0:3.3-12.el6_5 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x64-msi | 0:3.3-12.el6_5 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x86-cab | 0:3.3-12.el6_5 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x86-msi | 0:3.3-12.el6_5 · Red Hat:rhev_manager:3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:31 | 2018-04-21 |
| Proof-of-concept repository on GitHub | stars:5 | 2021-01-01 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+2043 d
- TodayNov 16, 2026+5175 d
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-19-115 · Aug 22, 2019(NGINX Sunucu Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- High
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:H/Au:N/C:P/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- code.google.com/p/chromium/issues/detail?id=139744
- isecpartners.com/blog/2012/9/14/details-on-the-crime-attack.html
- jvn.jp/en/jp/JVN65273415/index.html
- jvndb.jvn.jp/en/contents/2016/JVNDB-2016-000129.html
- lists.apple.com/archives/security-announce/2013/Jun/msg00000.html
- lists.fedoraproject.org/pipermail/package-announce/2013-April/101366.html
- lists.opensuse.org/opensuse-updates/2012-10/msg00096.html
- lists.opensuse.org/opensuse-updates/2013-01/msg00034.html
- lists.opensuse.org/opensuse-updates/2013-01/msg00048.html
- marc.info/?l=bugtraq&m=136612293908376&w=2
- news.ycombinator.com/item?id=4510829
- rhn.redhat.com/errata/RHSA-2013-0587.html
- security.stackexchange.com/questions/19911/crime-how-to-beat-the-beast-successor
- support.apple.com/kb/HT5784
- threatpost.com/en_us/blogs/crime-attack-uses-compression-ratio-tls-requests-side-channel-hijack-secure-sessions-091312
- threatpost.com/en_us/blogs/new-attack-uses-ssltls-information-leak-hijack-https-sessions-090512
- www.debian.org/security/2012/dsa-2579
- www.debian.org/security/2013/dsa-2627
- www.debian.org/security/2015/dsa-3253
Vendor advisories and official records. Exploit/PoC links are deliberately left out.