Podman 路径遍历漏洞导致 github.com/containers/podman 中任意文件读取/写入

攻击者可以利用此路径遍历漏洞绕过安全机制，访问或修改 Podman 容器内的文件系统。这可能导致敏感数据泄露，例如配置文件、密钥文件或用户数据。更严重的情况下，攻击者可能利用此漏洞在容器内执行恶意代码，从而控制整个系统。由于 Podman 广泛应用于容器化环境，该漏洞的潜在影响范围非常广泛，可能影响到多个应用程序和服务。

Organizations heavily reliant on containerization technologies, particularly those using Podman for development, testing, or production deployments, are at risk. Environments with shared hosting or multi-tenant container setups are especially vulnerable, as a compromise of one container could potentially impact others. Legacy Podman installations running older, unpatched versions are also at heightened risk.

• go / container: Inspect Podman container configurations for unusual file paths or access permissions.

ps aux | grep podman

• linux / server: Monitor system logs for suspicious file access attempts, particularly those involving traversal sequences (e.g., '../').

journalctl -u podman -f | grep "../"

• generic web: Examine Podman API endpoints for potential vulnerabilities related to file handling. Use curl to test for directory traversal.

curl 'http://localhost:8080/v1/containers/json?name=mycontainer&path=../../../../etc/passwd' #Example - adjust URL

1. 2024-08-20Disclosure

   disclosure

1. 已保留2019-03-27
2. 发布日期2024-08-20
3. 修改日期2026-03-03
4. EPSS 更新日期2026-04-02

最有效的缓解措施是升级到 Podman 1.4.0 或更高版本，该版本修复了此漏洞。如果无法立即升级，可以考虑使用访问控制列表 (ACL) 限制容器内的文件访问权限，或者使用安全容器运行时环境来隔离容器进程。此外，定期审查 Podman 的配置，确保没有不必要的权限或暴露的目录，也有助于降低风险。升级后，请验证 Podman 版本是否已成功升级。