Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2024-5187

Path Traversal in onnx (CVE-2024-5187)

Summary

path traversal in onnx (CVE-2024-5187). Successful exploitation can lead to full system takeover. Exploitable via ``download_model_with_test_data``. Mitigation: upgrade to `1.16.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-5187** has been found in onnx. Attackers can target a specific entry point like ``download_model_with_test_data`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: ?/10. What to do: upgrade onnx to **1.16.2** or later. If unsure, ask your IT team or search "onnx CVE-2024-5187" on the vendor's site.
CVE-2024-5187 (onnx) — CWE-22 / Attack vector: remote (network-reachable) / unauthenticated Attack surface: `download_model_with_test_data` Patched: `1.16.2` — 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 ``download_model_with_test_data`` without authentication.
📍 Affected scope
onnx — . Attack surface: `download_model_with_test_data`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.16.2**.
🛡️ 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

  1. 1
    Identify exposure identify 
    grep -r 'onnx' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `onnx` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade onnx to 1.16.2

    ステージング環境で 1.16.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI onnx
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.2"}]}]
pip onnx
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.16.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →