# CVE-2012-4929: Information disclosure in n/a

> Man-in-the-middle attackers can recover plaintext HTTP headers by observing encrypted data length differences in TLS implementations.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-4929, DSA-2627-1, GHSA-348j-44v2-vwfr, openSUSE-SU-2024:10531-1

## What is CVE-2012-4929?

CVE-2012-4929 is a low-severity vulnerability in Debian Debian Linux, published on 15 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-310

## Which versions are affected by CVE-2012-4929?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `links` | openSUSE:Tumbleweed | All versions | 2.13-1.3 |

Products: Debian Debian Linux, Google Chrome, Mozilla Firefox.

## How do I fix CVE-2012-4929?

Apply the vendor's patch.

## Is CVE-2012-4929 being exploited?

There is no known exploitation of CVE-2012-4929 in the wild and no public exploit code.

Public exploit code:

- :hocho: CRIME attack PoC : a compression oracle attacks CVE-2012-4929 :hocho: (github_poc): https://github.com/mpgn/CRIME-poc
- 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 (github_poc): https://github.com/anthophilee/A2SV--SSL-VUL-Scan

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4929 and fix it if it is affected.

What it is: CVE-2012-4929 is a low-severity vulnerability in Debian Debian Linux, published on 15 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-4929 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-4929/ (Markdown: https://insights.sbomify.com/CVE-2012-4929/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-4929
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-4929
- OSV: https://osv.dev/vulnerability/CVE-2012-4929

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-4929/
Summaries are generated and may contain mistakes; the official description above is the record.