← Back
CVE-2022-46292
Buffer Overflow in openbabel (CVE-2022-46292)
Summary
vulnerability in openbabel (CVE-2022-46292). Risk of unauthorized operations or information disclosure. Exploitable via ``obabel``. Mitigation: upgrade to `3.2.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-46292** has been found in openbabel.
Attackers can target a specific entry point like ``obabel`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade openbabel to **3.2.0** or later.
If unsure, ask your IT team or search "openbabel CVE-2022-46292" on the vendor's site.
CVE-2022-46292 (openbabel) — CWE-119 /
Attack surface: `obabel` / `OBConversion` / `fuzzregresstest`
Patched: `3.2.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-119) exists in openbabel. Attackers reach the vulnerable code path via ``obabel`` without authentication.
📍 Affected scope
openbabel — . Attack surface: `obabel` / `OBConversion` / `fuzzregresstest`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.2.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 'openbabel' .` 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 'openbabel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `openbabel` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openbabel to 3.2.0ステージング環境で 3.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
openbabel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.0"}]}]
References
- web https://github.com/openbabel/openbabel/security/advisories/GHSA-55f6-pf8r-c2f4
- web https://nvd.nist.gov/vuln/detail/CVE-2022-46292
- web https://github.com/openbabel/openbabel/commit/40e852138f21d586b7ccdce6329e7b23a87168bb
- web https://talosintelligence.com/vulnerability_reports/TALOS-2022-1666
- web https://www.talosintelligence.com/vulnerability_reports/TALOS-2022-1666
- web https://github.com/advisories/GHSA-55f6-pf8r-c2f4