CVE-2024-37891

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2024-37891
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-37891.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2024-37891
Aliases
Related
Published
2024-06-17T20:15:13Z
Modified
2024-10-12T11:25:10.983584Z
Summary
[none]
Details

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.

References

Affected packages

Debian:11 / python-urllib3

Package

Name
python-urllib3
Purl
pkg:deb/debian/python-urllib3?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

1.*

1.26.5-1~exp1
1.26.8-1
1.26.9-1
1.26.12-1
1.26.16-1
1.26.17-1
1.26.18-1
1.26.18-2

2.*

2.0.7-1
2.0.7-2

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / python-urllib3

Package

Name
python-urllib3
Purl
pkg:deb/debian/python-urllib3?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

1.*

1.26.12-1
1.26.16-1
1.26.17-1
1.26.18-1
1.26.18-2

2.*

2.0.7-1
2.0.7-2

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / python-urllib3

Package

Name
python-urllib3
Purl
pkg:deb/debian/python-urllib3?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

1.*

1.26.12-1
1.26.16-1
1.26.17-1
1.26.18-1
1.26.18-2

2.*

2.0.7-1
2.0.7-2

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Git / github.com/urllib3/urllib3

Affected ranges

Type
GIT
Repo
https://github.com/urllib3/urllib3
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
accff72ecc2f6cf5a76d9570198a93ac7c90270e

Affected versions

0.*

0.3
0.3.1
0.4
0.4.1

1.*

1.0
1.0.1
1.0.2
1.1
1.10
1.10.1
1.10.2
1.2
1.2.1
1.25
1.25.1
1.25.2
1.25.3
1.25.4
1.25.5
1.25.6
1.25.7
1.25.8
1.3
1.4
1.5
1.6
1.7
1.7.1
1.8
1.8.1
1.8.2
1.8.3
1.9
1.9.1

2.*

2.0.0
2.0.0a1
2.0.0a2
2.0.0a3
2.0.0a4
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
2.0.6
2.1.0
2.2.0
2.2.1

v2.*

v2.0.5