Skip to content

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

Package

pip scrapy (pip)

Affected versions

< 2.11.2

Patched versions

2.11.2

Description

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

Published by the National Vulnerability Database May 20, 2024
Published to the GitHub Advisory Database May 20, 2024
Reviewed May 20, 2024
Withdrawn May 20, 2024
Last updated May 20, 2024

Severity

High
7.5
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-cg34-w3fm-82h3

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.