CVE-2024-1968 Authorization Header Leakage in scrapy/scrapy on Scheme Change Redirects

2024-05-2008:03:43

CWE-200

@huntr_ai

www.cve.org

authorization header leakage

scrapy

scheme change redirects

fetch standard

sensitive information disclosure

7.5 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

7.1 High

AI Score

Confidence

High

0.0004 Low

EPSS

Percentile

9.0%

JSON

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.

CNA Affected

[
  {
    "vendor": "scrapy",
    "product": "scrapy/scrapy",
    "versions": [
      {
        "version": "unspecified",
        "lessThan": "2.11.2",
        "status": "affected",
        "versionType": "custom"
      }
    ]
  }
]