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.
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
|Base Score:||9.8||Base Metrics:||AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H|
|Access Vector:||Network||Attack Complexity:||Low|
|Privileges Required:||None||User Interaction:||None|
|Integrity Impact:||High||Availability Impact:||High|
|Oracle Linux version 7 (curl)||ELSA-2018-3157||2018-11-05|
|Oracle Linux version 7 (nss-pem)||ELSA-2018-3157||2018-11-05|
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team