← Back
CVE-2024-23346
Command Injection in pymatgen (CVE-2024-23346)
Summary
command injection in pymatgen (CVE-2024-23346). Successful exploitation can lead to full system takeover. Exploitable via ``pymatgen``. Mitigation: upgrade to `2024.2.20` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-23346** has been found in pymatgen.
Attackers can target a specific entry point like ``pymatgen`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade pymatgen to **2024.2.20** or later.
If unsure, ask your IT team or search "pymatgen CVE-2024-23346" on the vendor's site.
CVE-2024-23346 (pymatgen) — CWE-77 /
Attack vector: local / unauthenticated / no user interaction
Attack surface: `pymatgen` / `__builtins__` / `None` / `BuiltinImporter`
Patched: `2024.2.20` — 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-77) exists in pymatgen. Attackers reach the vulnerable code path via ``pymatgen`` without authentication.
📍 Affected scope
pymatgen — . Attack surface: `pymatgen` / `__builtins__` / `None` / `BuiltinImporter`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2024.2.20**.
🛡️ 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 'pymatgen' .` 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 'pymatgen' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pymatgen` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pymatgen to 2024.2.20ステージング環境で 2024.2.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pymatgen
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2024.2.20"}]}]
References
- advisory https://github.com/advisories/GHSA-vgv8-5cpj-qj2f
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-23346
- package https://github.com/materialsproject/pymatgen
- web https://github.com/materialsproject/pymatgen/security/advisories/GHSA-vgv8-5cpj-qj2f
- web https://www.vicarius.io/vsociety/posts/critical-security-flaw-in-pymatgen-library-cve-2024-23346
- web https://github.com/materialsproject/pymatgen/commit/c231cbd3d5147ee920a37b6ee9dd236b376bcf5a
- web https://github.com/materialsproject/pymatgen/blob/master/pymatgen/symmetry/settings.py#L97C1-L111C108
- web https://github.com/pypa/advisory-database/tree/main/vulns/pymatgen/PYSEC-2024-226.yaml