<?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://127.0.0.1:10001</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, 21 Nov 2026 16:52:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-45803 — Request body not stripped after redirect in urllib3</title>
      <link>https://127.0.0.1:10001/vuln/cve-2023-45803</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; urllib3&lt;/p&gt;
&lt;p&gt;urllib3 is a user-friendly HTTP client library for Python. urllib3 previously wouldn&amp;#39;t remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303 after the request had its method changed from one that could accept a request body (like `POST`) to `GET` as is required by HTTP RFCs. Although this behavior is not specified in the section for redirects, it can be inferred by piecing together information from different sections and we have observed the behavior in other major HTTP client implementations like curl and web browsers. Because the vulnerability requires a previously trusted service to become compromised in order to have an impact on confidentiality we believe the exploitability of this vulnerability is low. Additionally, many users aren&amp;#39;t putting sensitive data in HTTP request bodies, if this is the case then this vulnerability isn&amp;#39;t exploitable. Both of the following conditions must be true to be affected by this vulnerability: 1. Using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON) and 2. The origin service is compromised and starts redirecting using 301, 302, or 303 to a malicious peer or the redirected-to service becomes compromised. This issue has been addressed in versions 1.26.18 and 2.0.7 and users are advised to update to resolve this issue. Users unable to update should disable redirects for services that aren&amp;#39;t expecting to respond with redirects with `redirects=False` and disa…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; urllib3&lt;/p&gt;
&lt;p&gt;urllib3 is a user-friendly HTTP client library for Python. urllib3 previously wouldn&amp;#39;t remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303 after the request had its method changed from one that could accept a request body (like `POST`) to `GET` as is required by HTTP RFCs. Although this behavior is not specified in the section for redirects, it can be inferred by piecing together information from different sections and we have observed the behavior in other major HTTP client implementations like curl and web browsers. Because the vulnerability requires a previously trusted service to become compromised in order to have an impact on confidentiality we believe the exploitability of this vulnerability is low. Additionally, many users aren&amp;#39;t putting sensitive data in HTTP request bodies, if this is the case then this vulnerability isn&amp;#39;t exploitable. Both of the following conditions must be true to be affected by this vulnerability: 1. Using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON) and 2. The origin service is compromised and starts redirecting using 301, 302, or 303 to a malicious peer or the redirected-to service becomes compromised. This issue has been addressed in versions 1.26.18 and 2.0.7 and users are advised to update to resolve this issue. Users unable to update should disable redirects for services that aren&amp;#39;t expecting to respond with redirects with `redirects=False` and disa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cve-2023-45803</guid>
    </item>
    <item>
      <title>USN-6473-1 — python-urllib3 vulnerabilities</title>
      <link>https://127.0.0.1:10001/vuln/usn-6473-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: python-urllib3, Ubuntu:Pro:18.04:LTS: python-urllib3, Ubuntu:20.04:LTS: python-urllib3, Ubuntu:22.04:LTS: python-urllib3&lt;/p&gt;
&lt;p&gt;It was discovered that urllib3 didn&amp;#39;t strip HTTP Authorization header
on cross-origin redirects. A remote attacker could possibly use this 
issue to obtain sensitive information. This issue only affected
Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. (CVE-2018-25091)&lt;/p&gt;
&lt;p&gt;It was discovered that urllib3 didn&amp;#39;t strip HTTP Cookie header on 
cross-origin redirects. A remote attacker could possibly use this 
issue to obtain sensitive information. (CVE-2023-43804)&lt;/p&gt;
&lt;p&gt;It was discovered that urllib3 didn&amp;#39;t strip HTTP body on status code
303 redirects under certain circumstances. A remote attacker could 
possibly use this issue to obtain sensitive information. (CVE-2023-45803)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: python-urllib3, Ubuntu:Pro:18.04:LTS: python-urllib3, Ubuntu:20.04:LTS: python-urllib3, Ubuntu:22.04:LTS: python-urllib3&lt;/p&gt;
&lt;p&gt;It was discovered that urllib3 didn&amp;#39;t strip HTTP Authorization header
on cross-origin redirects. A remote attacker could possibly use this 
issue to obtain sensitive information. This issue only affected
Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. (CVE-2018-25091)&lt;/p&gt;
&lt;p&gt;It was discovered that urllib3 didn&amp;#39;t strip HTTP Cookie header on 
cross-origin redirects. A remote attacker could possibly use this 
issue to obtain sensitive information. (CVE-2023-43804)&lt;/p&gt;
&lt;p&gt;It was discovered that urllib3 didn&amp;#39;t strip HTTP body on status code
303 redirects under certain circumstances. A remote attacker could 
possibly use this issue to obtain sensitive information. (CVE-2023-45803)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/usn-6473-1</guid>
    </item>
  </channel>
</rss>
