← Back
GHSA-q56x-g2fj-4rj6
Path Traversal in onnx (GHSA-q56x-g2fj-4rj6)
Summary
path traversal in onnx (GHSA-q56x-g2fj-4rj6). Data can be tampered with by attackers. Exploitable via ``save_external_data``. Mitigation: upgrade to `1.21.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-q56x-g2fj-4rj6** has been found in onnx.
Attackers can target a specific entry point like ``save_external_data`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade onnx to **1.21.0** or later.
If unsure, ask your IT team or search "onnx GHSA-q56x-g2fj-4rj6" on the vendor's site.
GHSA-q56x-g2fj-4rj6 (onnx) — CWE-22 /
Attack vector: local / unauthenticated
Attack surface: `save_external_data` / `os.path.isfile` / `open` / `O_NOFOLLOW`
Patched: `1.21.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
**Path traversal** (CWE-22) exists in onnx. Attackers reach the vulnerable code path via ``save_external_data`` without authentication.
📍 Affected scope
onnx — . Attack surface: `save_external_data` / `os.path.isfile` / `open` / `O_NOFOLLOW`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **1.21.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 'onnx' .` 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 'onnx' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `onnx` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade onnx to 1.21.0ステージング環境で 1.21.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
onnx
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.21.0"}]}]
PyPI
onnx
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.21.0"}]}]