Authorization Header Leakage in scrapy/scrapy on Scheme Change Redirects
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| scrapy | scrapy/scrapy | affected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Scrapy | Scrapy | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-1419 | 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 GHSA |
GHSA-4qqq-9vqf-3h3f | Scrapy leaks the authorization header on same-domain but cross-origin redirects |
Ubuntu USN |
USN-7476-1 | Scrapy vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.688% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Scrapy
Scrapy scrapy |
|
| Weaknesses | NVD-CWE-noinfo | |
| CPEs | cpe:2.3:a:scrapy:scrapy:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Scrapy
Scrapy scrapy |