CVE-2018-1000007
mediumpriority · track · 42EPSS 0.099 · 96 %ileDEEURUUSEPSS · scored 2026-10-27
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–critical · 5–9.8
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (52)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2023-0890libcurl: Mehrere SchwachstellenDeutsch2018-01-24csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in libcurl ausnutzen, um einen Denial of Service Angriff durchzuführen oder vertrauliche Daten einzusehen.
- WID-SEC-W-2026-0180Dell Data Protection Advisor: Mehrere SchwachstellenDeutsch2026-01-20csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, Sicherheitsmaßnahmen zu umgehen und nicht näher spezifizierte Angriffe zu starten.
- CURL-CVE-2018-1000007HTTP authentication leak in redirects2018-01-24vendor · osvUS
curl might leak authentication data to third parties. When asked to send custom headers in its HTTP requests, curl sends that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the curl-using client's request.
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (55)
External citations — patches, advisories, analysis.
- http://www.ibm.com/support/docview.wss?uid=ibm10886247cnnvd
- http://www.ibm.com/support/docview.wss?uid=ibm10888299cnnvd
- http://www.openwall.com/lists/oss-security/2022/04/27/4cnnvd
- http://www.securitytracker.com/id/1040274cnnvd
- https://access.redhat.com/errata/RHBA-2019:0327cnnvd
- https://access.redhat.com/errata/RHSA-2018:3157cnnvd
- https://access.redhat.com/errata/RHSA-2018:3558cnnvd
- https://access.redhat.com/errata/RHSA-2019:1543cnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan