Bug 1955316 (CVE-2021-31879) - CVE-2021-31879 wget: authorization header disclosure on redirect
Summary: CVE-2021-31879 wget: authorization header disclosure on redirect
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2021-31879
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1955317 1971620 1971623 1973066 1973067 1973068 1973070
Blocks: 1955318
TreeView+ depends on / blocked
 
Reported: 2021-04-29 20:35 UTC by Guilherme de Almeida Suckevicz
Modified: 2024-01-09 15:46 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in wget. If wget sends an Authorization header as part of a query and receives an HTTP REDIRECT to a third party in return, the Authorization header will be forwarded as part of the redirected request. This issue creates a password leak, as the second server receives the password. The highest threat from this vulnerability is confidentiality.
Clone Of:
Environment:
Last Closed: 2021-11-15 13:19:12 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2021-04-29 20:35:16 UTC
GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.

If wget sends an Authorization header to a Web server, and that server replies with a REDIRECT, that header will not be stripped, and thus be forwarded to the second web server. This creates a password leak, as the 2nd server receives the password.

Reference:
https://mail.gnu.org/archive/html/bug-wget/2021-02/msg00002.html

Comment 1 Guilherme de Almeida Suckevicz 2021-04-29 20:35:33 UTC
Created wget tracking bugs for this issue:

Affects: fedora-all [bug 1955317]

Comment 2 Cedric Buissart 2021-06-14 13:06:07 UTC
This was previously reported upstream already in 2019 via :
https://savannah.gnu.org/bugs/?56909


Note You need to log in before you can comment on or make changes to this bug.