← Back
CVE-2024-37891
Vulnerability in urllib3 (CVE-2024-37891)
Summary
vulnerability in urllib3 (CVE-2024-37891). Confidential information can be exposed externally. Exploitable via ``ProxyManager``. Mitigation: upgrade to `2.2.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-37891** has been found in urllib3.
Attackers can target a specific entry point like ``ProxyManager`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade urllib3 to **2.2.2** or later.
If unsure, ask your IT team or search "urllib3 CVE-2024-37891" on the vendor's site.
CVE-2024-37891 (urllib3) — CWE-669 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `ProxyManager`
Patched: `2.2.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-669) exists in urllib3. Attackers reach the vulnerable code path via ``ProxyManager`` without authentication.
📍 Affected scope
urllib3 — . Attack surface: `ProxyManager`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.2.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'urllib3' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'urllib3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `urllib3` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade urllib3 to 2.2.2ステージング環境で 2.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
urllib3
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.2.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-37891
- advisory https://github.com/advisories/GHSA-34jh-p97f-mpxf
- package https://github.com/urllib3/urllib3
- package https://pypi.org/project/urllib3
- web https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf
- web https://github.com/urllib3/urllib3/commit/40b6d1605814dd1db0a46e202d6e56f2e4c9a468
- web https://github.com/urllib3/urllib3/commit/accff72ecc2f6cf5a76d9570198a93ac7c90270e
- web https://lists.debian.org/debian-lts-announce/2024/12/msg00020.html
- web https://security.netapp.com/advisory/ntap-20240822-0003
- web https://www.vicarius.io/vsociety/posts/proxy-authorization-header-handling-vulnerability-in-urllib3-cve-2024-37891