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.

The remote Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-7476-1 advisory.

    It was discovered that Scrapy improperly exposed HTTP authentication

    credentials to request targets, including during redirects. An attacker

    could use this issue to gain unauthorized access to user accounts. This issue only affected Ubuntu 18.04     LTS and Ubuntu 20.04 LTS. (CVE-2021-41125)

    It was discovered that Scrapy did not remove the cookie header during cross-domain redirects. An attacker     could possibly use this issue to gain unauthorized access to user accounts. This issue only affected     Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2022-0577)

    It was discovered that Scrapy inefficiently parsed XML content. An attacker could use this issue to cause     a denial of service by sending a crafted XML response. This issue only affected Ubuntu 18.04 LTS, Ubuntu     20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2024-1892)

    It was discovered that Scrapy did not properly check response size during decompression. An attacker could     send a crafted response that would exhaust memory and cause a denial of service. This issue only affected     Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2024-3572)

    It was discovered that Scrapy did not remove the authorization header during cross-domain redirects. An     attacker could possibly use this issue to gain unauthorized access to user accounts. This issue only     affected

    Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2024-3574)

    It was discovered that Scrapy did not remove the authorization header during redirects that change scheme     but remain in the same domain. This issue could possibly be used by an attacker to expose sensitive

    information or to gain unauthorized access to user accounts. (CVE-2024-1968)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2024-1968)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2024-1968)

The remote Fedora 39 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2024-0bd3b1212e advisory.

    - Update to 2.11.2


Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Fedora 40 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2024-c27b82d702 advisory.

    - Update to 2.11.2


Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
235158	Ubuntu 18.04 LTS / 20.04 LTS / 22.04 LTS / 24.04 LTS : Scrapy vulnerabilities (USN-7476-1)	Nessus	Ubuntu Local Security Checks	Local	medium
227825	Linux Distros Unpatched Vulnerability : CVE-2024-1968	Nessus	Misc.	Local	high
410349	SCA: security update for Scrapy (GHSA-4qqq-9vqf-3h3f)	Tenable Cloud Security	SCA Checks	Local	high
410349	SCA: security update for Scrapy (GHSA-4qqq-9vqf-3h3f)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
204818	Fedora 39 : python-scrapy (2024-0bd3b1212e)	Nessus	Fedora Local Security Checks	Local	high
204813	Fedora 40 : python-scrapy (2024-c27b82d702)	Nessus	Fedora Local Security Checks	Local	high

Detections

Analytics

CVE-2024-1968

high

Tenable Plugins

medium

high

high

high

high

high