← Back
CVE-2024-35195
Vulnerability in requests (CVE-2024-35195)
Summary
vulnerability in requests (CVE-2024-35195). Confidential information can be exposed externally. Exploitable via ``requests.Session``. Mitigation: upgrade to `2.32.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-35195** has been found in requests.
Attackers can target a specific entry point like ``requests.Session`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade requests to **2.32.0** or later.
If unsure, ask your IT team or search "requests CVE-2024-35195" on the vendor's site.
CVE-2024-35195 (requests) — CWE-670 /
Attack vector: local
Attack surface: `requests.Session` / `requests`
Patched: `2.32.0` — 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-670) exists in requests. Attackers reach the vulnerable code path via ``requests.Session`` without authentication.
📍 Affected scope
requests — . Attack surface: `requests.Session` / `requests`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.32.0**.
🛡️ 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 'requests' .` 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 'requests' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `requests` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade requests to 2.32.0ステージング環境で 2.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
requests
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.32.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-35195
- advisory https://github.com/advisories/GHSA-9wx4-h78v-vm56
- package https://github.com/psf/requests
- package https://pypi.org/project/requests
- web https://github.com/psf/requests/security/advisories/GHSA-9wx4-h78v-vm56
- web https://github.com/psf/requests/pull/6655
- web https://github.com/psf/requests/commit/a58d7f2ffb4d00b46dca2d70a3932a0b37e22fac
- web https://lists.fedoraproject.org/archives/list/[email protected]/message/IYLSNK5TL46Q6XPRVMHVWS63MVJQOK4Q
- web https://lists.fedoraproject.org/archives/list/[email protected]/message/N7WP6EYDSUOCOJYHDK5NX43PYZ4SNHGZ