<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 19:29:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-1968 — Authorization Header Leakage in scrapy/scrapy on Scheme Change Redirects</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-1968</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; scrapy/scrapy, scrapy&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; scrapy/scrapy, scrapy&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-1968</guid>
    </item>
    <item>
      <title>USN-7476-1 — python-scrapy vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7476-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: python-scrapy, Ubuntu:Pro:20.04:LTS: python-scrapy, Ubuntu:Pro:22.04:LTS: python-scrapy, Ubuntu:Pro:24.04:LTS: python-scrapy&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;It was discovered that Scrapy did not remove the authorization header
during redirects…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: python-scrapy, Ubuntu:Pro:20.04:LTS: python-scrapy, Ubuntu:Pro:22.04:LTS: python-scrapy, Ubuntu:Pro:24.04:LTS: python-scrapy&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;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)&lt;/p&gt;
&lt;p&gt;It was discovered that Scrapy did not remove the authorization header
during redirects…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7476-1</guid>
    </item>
  </channel>
</rss>
