← Back
CVE-2024-39689
Vulnerability in certifi (CVE-2024-39689)
Summary
vulnerability in certifi (CVE-2024-39689). Data can be tampered with by attackers. Exploitable via ``GLOBALTRUST``. Mitigation: upgrade to `bd8153872e9c6fc98f4023df9c2deaffea2fa463, 2024.7.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-39689** has been found in certifi.
Attackers can target a specific entry point like ``GLOBALTRUST`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade certifi to **bd8153872e9c6fc98f4023df9c2deaffea2fa463, 2024.7.4** or later.
If unsure, ask your IT team or search "certifi CVE-2024-39689" on the vendor's site.
CVE-2024-39689 (certifi) — CWE-345 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `GLOBALTRUST`
Patched: `bd8153872e9c6fc98f4023df9c2deaffea2fa463, 2024.7.4` — 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-345) exists in certifi. Attackers reach the vulnerable code path via ``GLOBALTRUST`` without authentication.
📍 Affected scope
certifi — . Attack surface: `GLOBALTRUST`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **bd8153872e9c6fc98f4023df9c2deaffea2fa463, 2024.7.4**.
🛡️ 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 'certifi' .` 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 'certifi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `certifi` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade certifi to bd8153872e9c6fc98f4023df9c2deaffea2fa463, 2024.7.4ステージング環境で bd8153872e9c6fc98f4023df9c2deaffea2fa463, 2024.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
certifi
[{"repo":"https:\/\/github.com\/certifi\/python-certifi","type":"GIT","events":[{"introduced":"0"},{"fixed":"bd8153872e9c6fc98f4023df9c2deaffea2fa463"}]},{"type":"ECOSYSTEM","events":[{"introduced":"2021.5.30"},{"fixed":"2024.7.4"}]}]
References
- advisory https://github.com/certifi/python-certifi/security/advisories/GHSA-248v-346w-9cwc
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-39689
- advisory https://security.netapp.com/advisory/ntap-20241206-0001/
- advisory https://github.com/advisories/GHSA-248v-346w-9cwc
- package https://github.com/certifi/python-certifi
- patch https://github.com/certifi/python-certifi/commit/bd8153872e9c6fc98f4023df9c2deaffea2fa463
- web https://github.com/pypa/advisory-database/tree/main/vulns/certifi/PYSEC-2024-230.yaml
- web https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/XpknYMPO8dI
- web https://security.netapp.com/advisory/ntap-20241206-0001