Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| artful | released | 7.55.1-1ubuntu2.3 |
| devel | not-affected | 7.58.0-2ubuntu1 |
| esm-infra-legacy/trusty | released | 7.35.0-1ubuntu2.14 |
| esm-infra/xenial | released | 7.47.0-1ubuntu2.6 |
| precise/esm | not-affected | 7.22.0-3ubuntu4.20 |
| trusty | released | 7.35.0-1ubuntu2.14 |
| trusty/esm | released | 7.35.0-1ubuntu2.14 |
| upstream | released | 7.58.0-1 |
| xenial | released | 7.47.0-1ubuntu2.6 |
Показывать по
EPSS
5 Medium
CVSS2
9.8 Critical
CVSS3
Связанные уязвимости
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.
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.
libcurl 7.1 through 7.57.0 might accidentally leak authentication data ...
EPSS
5 Medium
CVSS2
9.8 Critical
CVSS3