Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | 2.12.0-2 |
| esm-apps/bionic | released | 1.5.0-1ubuntu0.1~esm1 |
| esm-apps/focal | released | 1.7.3-1ubuntu0.1~esm1 |
| esm-apps/jammy | released | 2.5.1-2ubuntu0.1~esm1 |
| esm-apps/noble | released | 2.11.1-1ubuntu0.1~esm2 |
| esm-apps/xenial | ignored | changes too intrusive |
| focal | ignored | end of standard support, was needed |
| jammy | needed | |
| mantic | ignored | end of life, was needs-triage |
| noble | needed |
Показывать по
EPSS
7.5 High
CVSS3
Связанные уязвимости
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.
In scrapy/scrapy, an issue was identified where the Authorization head ...
Scrapy leaks the authorization header on same-domain but cross-origin redirects
EPSS
7.5 High
CVSS3