Headline
GHSA-cg34-w3fm-82h3: Duplicate Advisory: Scrapy leaks the authorization header on same-domain but cross-origin redirects
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-4qqq-9vqf-3h3f. This link is maintained to preserve external references.
Original Description
In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects that only change the scheme (e.g., HTTPS to HTTP) but remain within the same domain. This behavior contravenes the Fetch standard, which mandates the removal of Authorization headers in cross-origin requests when the scheme, host, or port changes. Consequently, when a redirect downgrades from HTTPS to HTTP, the Authorization header may be inadvertently exposed in plaintext, leading to potential sensitive information disclosure to unauthorized actors. The flaw is located in the _build_redirect_request function of the redirect middleware.
- GitHub Advisory Database
- GitHub Reviewed
- GHSA-cg34-w3fm-82h3
Duplicate Advisory: Scrapy leaks the authorization header on same-domain but cross-origin redirects
High severity GitHub Reviewed Published May 20, 2024 to the GitHub Advisory Database • Updated May 20, 2024
Withdrawn This advisory was withdrawn on May 20, 2024
Affected versions
< 2.11.2
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-4qqq-9vqf-3h3f. This link is maintained to preserve external references.
Original Description
In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects that only change the scheme (e.g., HTTPS to HTTP) but remain within the same domain. This behavior contravenes the Fetch standard, which mandates the removal of Authorization headers in cross-origin requests when the scheme, host, or port changes. Consequently, when a redirect downgrades from HTTPS to HTTP, the Authorization header may be inadvertently exposed in plaintext, leading to potential sensitive information disclosure to unauthorized actors. The flaw is located in the _build_redirect_request function of the redirect middleware.
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-1968
- scrapy/scrapy@1d0502f
- https://huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a
Published by the National Vulnerability Database
May 20, 2024
Published to the GitHub Advisory Database
May 20, 2024
Last updated
May 20, 2024