paddlepaddle/paddle 2.6未満におけるパス・トラバーサルによる任意のファイル上書き

The core of this vulnerability lies in PaddlePaddle's insufficient validation of user-supplied file paths. An attacker can craft malicious input that bypasses these checks, allowing them to specify a path outside the intended directory. This enables the overwriting of critical system files, configuration files, or even executable code. Successful exploitation could result in remote code execution, data corruption, denial of service, or complete system takeover. The impact is particularly severe given PaddlePaddle's use in machine learning and AI applications, where compromised models or data could have far-reaching consequences.

Organizations and individuals utilizing PaddlePaddle for machine learning and AI development are at risk. This includes researchers, data scientists, and developers deploying PaddlePaddle-based applications in production environments. Systems with older, unpatched PaddlePaddle installations are particularly vulnerable.

• python / supply-chain:

import os
import subprocess
# Check PaddlePaddle version
result = subprocess.run(['python', '-c', 'import paddle; print(paddle.__version__)'], capture_output=True, text=True)
version = result.stdout.strip()
if version <= '2.5':
    print('PaddlePaddle version is vulnerable!')

• generic web: Check for unusual file modifications in system logs. Monitor PaddlePaddle processes for unexpected file access patterns. • generic web: Examine PaddlePaddle configuration files for any signs of tampering or unauthorized modifications.

1. 2024-03-07Disclosure

   disclosure

2. 2024-03-07Patch

   patch

1. 予約済み2024-01-23
2. 公開日2024-03-07
3. 更新日2025-02-13
4. EPSS 更新日2026-04-02

The primary mitigation for CVE-2024-0818 is to immediately upgrade to PaddlePaddle version 2.6 or later. If upgrading is not immediately feasible due to compatibility issues or testing requirements, consider implementing strict input validation on file paths within your application code. While not a complete solution, restricting access to sensitive directories and implementing file integrity monitoring can help limit the potential damage. Consider using a Web Application Firewall (WAF) with path traversal protection rules, though this is less effective than patching the underlying vulnerability. After upgrade, confirm by attempting to trigger the vulnerable functionality and verifying that file access is properly restricted.