Authorization Header Leak During Cross-Domain Redirect in scrapy/scrapy
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 |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Scrapy | Scrapy | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-0622 | In scrapy version 2.10.1, an issue was identified where the Authorization header, containing credentials for server authentication, is leaked to a third-party site during a cross-domain redirect. This vulnerability arises from the failure to remove the Authorization header when redirecting across domains. The exposure of the Authorization header to unauthorized actors could potentially allow for account hijacking. |
Github GHSA |
GHSA-cw9j-q3vf-hrrv | Scrapy authorization header leakage on cross-domain redirect |
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.648% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:scrapy:scrapy:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|