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.
leosilvafor precise some files that patch the code are not present
Source: curl (LP Ubuntu Debian)
Upstream:released (7.58.0-1)
Ubuntu 12.04 ESM (Precise Pangolin):released (7.22.0-3ubuntu4.20)
Ubuntu 14.04 ESM (Trusty Tahr):released (7.35.0-1ubuntu2.14)
Ubuntu 16.04 LTS (Xenial Xerus):released (7.47.0-1ubuntu2.6)
Ubuntu 18.04 LTS (Bionic Beaver):not-affected (7.58.0-2ubuntu1)
More Information

Updated: 2020-09-10 05:47:44 UTC (commit 81a23a978c4436cd99e1d040e9e73e9146876281)