<?xml version="1.0" encoding="utf-8"?>
  <cvrfdoc xmlns="http://www.icasi.org/CVRF/schema/cvrf/1.1" xmlns:cvrf="http://www.icasi.org/CVRF/schema/cvrf/1.1">
    <DocumentTitle>An update for python-urllib3 is now available for HCE 2.0</DocumentTitle>
    <DocumentType>Security Advisory</DocumentType>
    <DocumentPublisher Type="Vendor">
      <ContactDetails>hws_security@huawei.com</ContactDetails>
      <IssuingAuthority>Huawei Cloud</IssuingAuthority>
    </DocumentPublisher>
    <DocumentTracking>
      <Identification>
        <ID>HCE2-SA-2024-0257</ID>
      </Identification>
      <Status>Final</Status>
      <Version>1.0</Version>
      <RevisionHistory>
        <Revision>
          <Number>1.0</Number>
          <Date>2024-09-23T10:09:48:00Z</Date>
          <Description>current version</Description>
        </Revision>
      </RevisionHistory>
      <InitialReleaseDate>2024-09-23T10:09:48:00Z</InitialReleaseDate>
      <CurrentReleaseDate>2024-09-23T10:09:48:00Z</CurrentReleaseDate>
      <Generator>
        <Engine>HCE SA Engine 1.0.0</Engine>
      </Generator>
    </DocumentTracking>
    <DocumentNotes>
      <Note Type="Summary" Ordinal="001">An update for python-urllib3 is now available for HCE 2.0

HCE Security has rated this update as having a security impact of Moderate.A Common Vunlnerability Scoring System(CVSS)base score, which gives a detailed severity rating, is available for each vulnerability from the CVElink(s) in the References section.</Note>
      <Note Type="General" Ordinal="002">Security Fix(es):

 urllib3 is a user-friendly HTTP client library for Python. When using urllib3_x27;s proxy support with `ProxyManager`, the `Proxy-Authorization` header is only sent to the configured proxy, as expected. However, when sending HTTP requests *without* using urllib3_x27;s proxy support, it_x27;s possible to accidentally configure the `Proxy-Authorization` header even though it won_x27;t have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn_x27;t treat the `Proxy-Authorization` HTTP header as one carrying authentication material and thus doesn_x27;t strip the header on cross-origin redirects. Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the `Proxy-Authorization` header during cross-origin redirects to avoid the small chance that users are doing this on accident. Users should use urllib3_x27;s proxy support or disable automatic redirects to achieve safe processing of the `Proxy-Authorization` header, but we still decided to strip the header by default in order to further protect users who aren_x27;t using the correct approach. We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited: 1. Setting the `Proxy-Authorization` header without using urllib3_x27;s built-in proxy support. 2. Not disabling HTTP redirects. 3. Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin. Users are advised to update to either version 1.26.19 or version 2.2.2. Users unable to upgrade may use the `Proxy-Authorization` header with urllib3_x27;s `ProxyManager`, disable HTTP redirects using `redirects=False` when sending requests, or not user the `Proxy-Authorization` header as mitigations. (CVE-2024-37891)
</Note>
      <Note Type="Legal Disclaimer" Ordinal="003">This document is provided on an &quot;AS IS&quot; basis and does not implyany kind of guarantee or warranty, either express or implied, including the warranties of merchantability or fitness for a particular purpose. In no eventshall Huawei or any of its directly or indirectly controlled subsidiaries or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages. Your use of the document, by any means, is totally at your own risk. Huawei is entitled to amend or update this document from time to time.
The information and data embodied in this document and any attachment are strictly confidential information of Huawei and are supplied on the understanding that they will be held confidentially and not disclosed to third parties without the prior written consent of Huawei. Use all reasonable efforts to protect the confidentiality of information. In particular, do not directly or indirectly disclose, allow access to, transmit or transfer information to a third party without our prior written consent. Thank you for your co-operation. Receipt of this security advisory shall be deemed as your consent of the terms and conditions above.</Note>
    </DocumentNotes>
    <DocumentReferences/>
    <ProductTree xmlns="http://www.icasi.org/CVRF/schema/prod/1.1">
      <Branch Type="Vendor" Name="HuaweiCloud">
        <Branch Type="Product Name" Name="HCE">
          <Branch Type="Product Version" Name="2.0">
            <FullProductName ProductID="HCE 2.0" CPE="cpe:/o:huawei:HCE:2.0">Huawei Cloud EulerOS 2.0</FullProductName>
          </Branch>
        </Branch>
      </Branch>
      <Branch Type="Product Version" Name="python-urllib3">
        <FullProductName ProductID="python-urllib3" CPE="cpe:/o:huawei:HCE:2.0">python-urllib3</FullProductName>
      </Branch>
      <Relationship ProductReference="python-urllib3" RelationType="Default Component Of" RelatesToProductReference="HCE 2.0"/>
    </ProductTree>
    <Vulnerability xmlns="http://www.icasi.org/CVRF/schema/vuln/1.1" Ordinal="001">
      <Notes>
        <Note Type="Details" Ordinal="001">This vulnerability can be exploited only when the following conditions are present:
None Vulnerability details: For technical details, customers are advised to reference the website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-37891</Note>
      </Notes>
      <Involvements>
        <Involvement Party="Vendor" Status="Completed"/>
      </Involvements>
      <CVE>CVE-2024-37891</CVE>
      <ProductStatuses>
        <Status Type="Fixed">
          <ProductID>HCE 2.0:python-urllib3-1.26.7-2.r8.hce2</ProductID>
        </Status>
      </ProductStatuses>
      <Threats>
        <Threat Type="Impact">
          <Description>For technical details, customers are advised to referencethe website: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-37891</Description>
        </Threat>
      </Threats>
      <CVSSScoreSets>
        <ScoreSet>
          <BaseScore>4.4</BaseScore>
          <Vector>CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N</Vector>
        </ScoreSet>
      </CVSSScoreSets>
      <Remediations/>
    </Vulnerability>
  </cvrfdoc>
