9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
0.006 Low
EPSS
Percentile
77.6%
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.
Author | Note |
---|---|
leosilva | for precise some files that patch the code are not present |
9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:L/Au:N/C:P/I:N/A:N
0.006 Low
EPSS
Percentile
77.6%