CVE-2020-11652: SaltStack Salt Path Traversal
SaltStack Salt · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CVE record)
- 6.5
- medium
- EPSS (exploit probability, 30 days)
- 86%
- higher than 99.7% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Ubuntu priority
- medium
CVE-2020-11652 explained
CVE-2020-11652 is a path traversal flaw in the SaltStack Salt master. Methods exposed by the salt-master ClearFuncs class do not properly sanitize paths, letting authenticated users access arbitrary directories. CISA lists it as known to be exploited, so unpatched Salt masters should be treated as a priority.
Impact
An attacker with low-privileged authenticated access to the salt-master over the network can reach arbitrary directories on the master. No user interaction is needed and attack complexity is low. The CVSS vector rates confidentiality impact as high, with no direct integrity or availability impact. This means sensitive files on the master could be exposed. Affected upstream versions are Salt before 2019.2.4 and 3000 before 3000.2.
Who is affected
The salt source package is affected on Ubuntu 14.04 LTS, 16.04 LTS and 18.04 LTS, and all three have fixed versions. Ubuntu 14.04 LTS is fixed in 0.17.5+ds-1ubuntu0.1~esm2, available only through Ubuntu Pro (ESM). Ubuntu 16.04 LTS is fixed in 2015.8.8+ds-1ubuntu0.1. Ubuntu 18.04 LTS is fixed in 2017.7.4+dfsg1-1ubuntu18.04.2. Both are in the standard archive. Ubuntu 14.04 LTS and 16.04 LTS are end of life. Standard support for 18.04 LTS has ended.
Written with AI from the data on this page and checked against it automatically.
Official description
An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class allows access to some methods that improperly sanitize paths. These methods allow arbitrary directory access to authenticated users.
CISA required action: Apply updates per vendor instructions.
CISA notes
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 18.04 LTS·salt
Fixed: 2017.7.4+dfsg1-1ubuntu18.04.2
Ubuntu 16.04 LTS·salt
ESM ended
Fixed: 2015.8.8+ds-1ubuntu0.1
Ubuntu 14.04 LTS·salt
fix via Ubuntu Pro
Fixed: 0.17.5+ds-1ubuntu0.1~esm2
What to do
- Identify all hosts running the salt-master service, as the flaw is in the master process.
- Update the
saltpackages to the fixed version for your release. - Restart the salt-master service so it stops running the vulnerable code.
- On Ubuntu 14.04 LTS, enable Ubuntu Pro (ESM) to receive
0.17.5+ds-1ubuntu0.1~esm2. - Restrict network access to the Salt master to trusted minions and administrators.
- Plan upgrades of end-of-life releases to a supported Ubuntu release.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace salt with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="salt"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="salt"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Partial – limited control or information
Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Questions about CVE-2020-11652
- Is this vulnerability exploited in practice?
- Yes. CISA added CVE-2020-11652 to its Known Exploited Vulnerabilities catalog on 2021-11-03. Its required action is to apply updates per vendor instructions. Whether it has been used in ransomware campaigns is listed as unknown.
- Does an attacker need credentials?
- Yes. The description says the arbitrary directory access is available to authenticated users. The CVSS vector rates required privileges as low and the attack vector as network.
- Do I need to restart anything after updating?
- Yes. Restart the salt-master service after installing the fixed
saltpackage. Until it is restarted, the running process keeps using the old, vulnerable code.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Other advisories
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.