CVE-2014-3563
NoneCVSS
—
EPSS
0.4%
Published
Aug 22, 2014
CISA due date
—
Cloudanix analysis
An old flaw in Salt configuration software lets someone already on a machine manipulate temporary files to gain full control of the system.
- Exploitation
- Local Privilege
- Attacker needs
- Local User
- Complexity
- Low
- Impact
- Full Compromise
- Component
- Application
- Class
- Path Traversal
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Local attackers can abuse insecure temporary file creation in seed.py, salt-ssh, and salt-cloud to perform path traversal, enabling arbitrary file read/write or symlink attacks that result in full system compromise.
Why it matters to the business
Compromise of Salt-managed infrastructure can lead to loss of control over servers and configurations, with high urgency for any remaining legacy deployments given the 2014 publication and complete impact on confidentiality, integrity, and availability.
How an attack unfolds
A local attacker identifies writable directories used by the affected components, creates malicious symlinks or races file creation, then triggers Salt operations in seed.py, salt-ssh, or salt-cloud to traverse paths and access or alter sensitive files.
How to fix it
Upgrade Salt to version 2014.1.10 or later; avoid running untrusted local processes on Salt minions and ensure temporary directories use appropriate permissions.
How to confirm the fix worked
Verify Salt version is 2014.1.10 or newer via salt --version; audit code and configurations for any remaining custom temp-file handling in the listed components.
Typical attack path
- Gain local access on a host running vulnerable Salt components
- Identify temporary file paths created by seed.py, salt-ssh, or salt-cloud
- Create symlinks or perform TOCTOU race to redirect file operations
- Trigger Salt commands that process the temporary files to achieve path traversal
- Read or write arbitrary files to escalate privileges or persist
How to detect it
Examine system and application logs around Salt process execution for unexpected file operations or permission changes in temporary directories; review historical access to seed.py, salt-ssh, and salt-cloud related paths.
What your security team should do
- Immediately upgrade all Salt installations to 2014.1.10 or a supported later release
- Review and restrict local user access on systems running Salt components
- Monitor for any legacy instances still running versions prior to 2014.1.10
The record
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| PyPI | salt | 0 | 2014.1.10 |
| Ubuntu:Pro:14.04:LTS | salt | 0 | 0.17.5+ds-1ubuntu0.1~esm1 |
| Ubuntu:Pro:16.04:LTS | salt | 0 | 2015.8.8+ds-1ubuntu0.1+esm1 |
| pypi | salt | 2014.1.0 | No fix |
Related vulnerabilities
- GHSA-77w2-v593-vxvv Salt junos Module Vulnerable to Code Injection via Specially Crafted YAML Payload Also affects salt
- GHSA-vcf3-26xf-fw4m Salt Authentication Protocol Version Downgrade Allows Minion Impersonation Also affects salt
- CVE-2025-62349 Salt contains an authentication protocol version downgrade weakness that can allow a… Also affects salt
- CVE-2025-62348 Salt's junos execution module contained an unsafe YAML decode/load usage. Also affects salt
- CVE-2023-34049 The Salt-SSH pre-flight option copies the script to the target at a predictable path… Also affects salt
- CVE-2024-22232 A specially crafted url can be created which leads to a directory traversal in the salt… Also affects salt
- CVE-2024-22231 Syndic cache directory creation is vulnerable to a directory traversal attack in salt… Also affects salt
- CVE-2026-113724 virtualenv is a tool for creating isolated virtual python environments. CWE-59