# CVE-2007-5034: Information disclosure in n/a

> Remote attackers can sniff sensitive POST data sent over HTTPS if a proxy is configured, due to cleartext leakage in CONNECT requests.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 21 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5034, DSA-1380-1, GHSA-ff3h-vr24-34v2, RHSA-2007:0933

## What is CVE-2007-5034?

CVE-2007-5034 is a medium-severity vulnerability in n/a, published on 21 Sep 2007. 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

ELinks before 0.11.3, when sending a POST request for an https URL, appends the body and content headers of the POST request to the CONNECT request in cleartext, which allows remote attackers to sniff sensitive data that would have been protected by TLS.  NOTE: this issue only occurs when a proxy is defined for https.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2007-5034?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elinks` | Red Hat:enterprise_linux:4::as | All versions | 0:0.9.2-3.3.5.2 |
| `elinks-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.9.2-3.3.5.2 |
| `elinks` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.9.2-3.3.5.2 |
| `elinks-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.9.2-3.3.5.2 |
| `elinks` | Red Hat:enterprise_linux:4::es | All versions | 0:0.9.2-3.3.5.2 |
| `elinks-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:0.9.2-3.3.5.2 |
| `elinks` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.9.2-3.3.5.2 |
| `elinks-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.9.2-3.3.5.2 |
| `elinks` | Red Hat:enterprise_linux:5::client | All versions | 0:0.11.1-5.1.0.1.el5 |
| `elinks-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.11.1-5.1.0.1.el5 |
| `elinks` | Red Hat:enterprise_linux:5::server | All versions | 0:0.11.1-5.1.0.1.el5 |
| `elinks-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.11.1-5.1.0.1.el5 |

Products: Elinks Elinks.

## How do I fix CVE-2007-5034?

Upgrade to a fixed version.

## Is CVE-2007-5034 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7224](https://insights.sbomify.com/CVE-2008-7224/): Memory corruption in n/a (high 7.8)
- [CVE-2006-5925](https://insights.sbomify.com/CVE-2006-5925/): Command injection in n/a (high 7.5)
- [CVE-2012-6709](https://insights.sbomify.com/CVE-2012-6709/): Security feature bypass in n/a (medium 5.9)
- [CVE-2012-4545](https://insights.sbomify.com/CVE-2012-4545/): Auth bypass in n/a (medium 5.1)
- [CVE-2002-1405](https://insights.sbomify.com/CVE-2002-1405/): Other in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5034 and fix it if it is affected.

What it is: CVE-2007-5034 is a medium-severity vulnerability in n/a, published on 21 Sep 2007. 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-2007-5034 in the wild and no public exploit code.

Affected product: n/a. 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-2007-5034/ (Markdown: https://insights.sbomify.com/CVE-2007-5034/index.md)
```

## Sources

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

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