Skip to content
Fencer Vulns
medium 4.3

CVE-2007-5034 json

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…

published 2007-09-21 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5015

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.6%
EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

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.

Patch / fix

  • elinks Debian 14, Debian 13, Debian 12 0.11.1-1.5

debian advisories DEBIAN-CVE-2007-5034

  • elinks RHEL 4 0.9.2-3.3.5.2
  • elinks RHEL 5 0.11.1-5.1.0.1.el5

red hat advisories RHSA-2007:0933

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2007-5034 updated

elinks reveals POST data to HTTPS proxy

  • Red Hat Enterprise Linux (v. 5 server) elinks 0.11.1-5.1.0.1.el5 Red Hat Enterprise Linux AS version 4 elinks 0.9.2-3.3.5.2 Red Hat Enterprise Linux Desktop (v. 5 client) elinks 0.11.1-5.1.0.1.el5 Red Hat Enterprise Linux Desktop version 4 elinks 0.9.2-3.3.5.2 Red Hat Enterprise Linux ES version 4 elinks 0.9.2-3.3.5.2 Red Hat Enterprise Linux WS version 4 elinks 0.9.2-3.3.5.2
    fixed: vendor fix RHSA-2007:0933

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.60% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.