<p>Upgrade <code>Amazon-Linux:2</code> <code>libcurl-devel</code> to version 0:7.55.1-9.amzn2.0.1 or higher.<br>This issue was patched in <code>ALAS2-2018-951</code>.</p>

Information Exposure Affecting libcurl-devel package, versions <0:7.55.1-9.amzn2.0.1

Threat Intelligence

0.57% (78^th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk ID SNYK-AMZN2-LIBCURLDEVEL-1660801
published 27 Sep 2021
disclosed 24 Jan 2018

Report a new vulnerability Found a mistake?

Introduced: 24 Jan 2018

CVE-2018-1000007 Open this link in a new tab CWE-200 Open this link in a new tab

How to fix?

Upgrade Amazon-Linux:2 libcurl-devel to version 0:7.55.1-9.amzn2.0.1 or higher.
This issue was patched in ALAS2-2018-951.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl-devel package and not the libcurl-devel package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

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.

References

CVSS Scores

version 3.1

Attack Vector (AV)

Network
Attack Complexity (AC)

Low
Privileges Required (PR)

None
User Interaction (UI)

None

Scope (S)

Unchanged

Confidentiality (C)

High
Integrity (I)

High
Availability (A)

High