CVE-2012-4929

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

4.3% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2012-09-15 18:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:45 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 4.3% in the next 30 days (EPSS).
• Severity: 2.6 LOW (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2012-09-15 18:55 UTC

Last modified

2026-06-16 23:45 UTC

Exploit probability

4.3% · EPSS, next 30 days

Weakness

CWE-310

Record status

Modified

Affected

• Debian Linux 7.0
• Debian Linux 8.0
• Google Chrome
• Mozilla Firefox

Attack profile CVSS 2.0 · 2.6

Attack vector

Network

Complexity

High

Authentication

None

Confidentiality

Partial

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2012-4929.md and follow it. Check whether this project is affected by CVE-2012-4929. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge