Onnx Directory Traversal Schwachstelle

The Directory Traversal vulnerability in onnx allows an attacker to read arbitrary files on the system where the onnx model is being processed. This could lead to the exposure of sensitive data such as configuration files, credentials, or even source code. The attacker's ability to read arbitrary files depends on the permissions of the process running the onnx model. This vulnerability bypasses a previous mitigation for CVE-2022-25882, indicating a potential for similar exploitation patterns. The blast radius extends to any application utilizing vulnerable onnx models, potentially impacting machine learning pipelines and inference services.

Organizations deploying ONNX Runtime in production environments, particularly those using it for machine learning inference with untrusted data, are at significant risk. This includes developers integrating ONNX Runtime into their applications and those relying on shared hosting environments where the ONNX Runtime installation may be managed by the provider.

• python / supply-chain:

import os
import subprocess
# Check ONNX Runtime version
result = subprocess.run(['onnxruntime', '--version'], capture_output=True, text=True)
version = result.stdout.splitlines()[0]
if version <= '1.9.0':
    print("ONNX Runtime version is vulnerable.")

• generic web: Check for ONNX Runtime endpoints exposed in your web application. Use curl to probe for potential file access vulnerabilities.

curl 'http://your-application/onnxruntime/model?external_data=/etc/passwd'

1. 2024-02-23Disclosure

   disclosure

1. Reserviert2024-02-23
2. Veröffentlicht2024-02-23
3. Geändert2026-02-04
4. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2024-27318 is to upgrade the onnx package to version 1.16.0 or later. If upgrading is not immediately feasible, consider implementing input validation on the externaldata field to restrict the allowed file paths. Additionally, restrict the permissions of the process running the onnx model to minimize the potential impact of a successful exploit. Review and update any existing WAF rules to detect and block requests containing malicious file paths in the externaldata field. After upgrading, confirm the fix by attempting to load a model with a crafted external_data path and verifying that access is denied.