Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2024-37891

Publication date 17 June 2024

Last updated 31 October 2024

Ubuntu priority

Low

Why this priority?

urllib3 is a user-friendly HTTP client library for Python. When using urllib3'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's proxy support, it's possible to accidentally configure the `Proxy-Authorization` header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the `Proxy-Authorization` HTTP header as one carrying authentication material and thus doesn'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'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'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'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's `ProxyManager`, disable HTTP redirects using `redirects=False` when sending requests, or not user the `Proxy-Authorization` header as mitigations.

Read the notes from the security team

Why is this CVE low priority?

Per urllib3 developers, this is a highly unlikely scenario

Learn more about Ubuntu priority

Status

Package Ubuntu Release Status
python-pip 24.10 oracular
Fixed 24.2+dfsg-1ubuntu0.1
24.04 LTS noble
Fixed 24.0+dfsg-1ubuntu1.1
23.10 mantic Ignored end of life, was needs-triage
22.04 LTS jammy
Fixed 22.0.2+dfsg-1ubuntu0.5
20.04 LTS focal
Fixed 20.0.2-5ubuntu1.11
18.04 LTS bionic
16.04 LTS xenial
14.04 LTS trusty
Needs evaluation
python-urllib3 24.10 oracular
Fixed 2.0.7-2ubuntu0.1
24.04 LTS noble
Fixed 2.0.7-1ubuntu0.1
23.10 mantic Ignored end of life, was needs-triage
22.04 LTS jammy
Fixed 1.26.5-1~exp1ubuntu0.2
20.04 LTS focal
Fixed 1.25.8-2ubuntu0.4
18.04 LTS bionic
16.04 LTS xenial
14.04 LTS trusty
Needs evaluation

Get expanded security coverage with Ubuntu Pro

Reduce your average CVE exposure time from 98 days to 1 day with expanded CVE patching, ten-years security maintenance and optional support for the full stack of open-source applications. Free for personal use.

Get Ubuntu Pro

Notes

mdeslaur

On focal and earlier, the python-pip package bundles python-urllib3 binaries when built. After updating python-urllib3, a no-change rebuild of python-pip is required. On jammy and later, python-urllib3 is bundled in the python-pip package and needs to be patched.

Patch details

For informational purposes only. We recommend not to cherry-pick updates. How can I get the fixes?

Package Patch details
python-pip
python-urllib3

References

Related Ubuntu Security Notices (USN)

Other references