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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published: 2018-01-24T22:00:00

Updated: 2024-08-05T12:33:48.439Z

Reserved: 2018-01-22T00:00:00

Link: CVE-2018-1000007

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2018-01-24T22:29:00.353

Modified: 2022-06-13T19:10:03.833

Link: CVE-2018-1000007

cve-icon Redhat

Severity : Moderate

Publid Date: 2018-01-24T00:00:00Z

Links: CVE-2018-1000007 - Bugzilla