CVE-2020-11651: SaltStack Salt Remote Code Execution

salt Updated 02 Oct 2025

Summary

30/04/2020
Yes i
Critical
9.8

CVE-2020-11651: An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. Affects salt across 2 version ranges.

< 2019.2.4 >= 3000, < 3000.2

Fixed in 2019.2.4 or 3000.2, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

SaltStack Salt is an open-source configuration management and remote execution framework. It is designed to manage and automate the infrastructure of large-scale computer systems. The vulnerability identified as CVE-2020-11651 affects versions of SaltStack Salt before 2019.2.4 and 3000 before 3000.2. This vulnerability allows remote users to access certain methods without authentication, potentially leading to the retrieval of user tokens from the salt master and the execution of arbitrary commands on salt minions.

Vulnerability Detail

The vulnerability lies within the salt-master process ClearFuncs class, which fails to properly validate method calls. This oversight enables remote users to exploit the system by accessing specific methods without authentication. By doing so, they can retrieve user tokens from the salt master and execute arbitrary commands on salt minions. This vulnerability poses a significant risk to the confidentiality, integrity, and availability of the affected systems.

How To Fix

Latest published version: 3008.3.0 as of 22 Oct 2026

pip install --upgrade "salt==3008.3.0"

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 2019.2.4 2019.2.4
    pip install --upgrade "salt==2019.2.4"
  • >= 3000, < 3000.2 3000.2
    pip install --upgrade "salt==3000.2"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, users can implement network-level access controls to restrict access to the salt-master process. This can be achieved by configuring firewalls or other network security measures to only allow trusted sources to communicate with the salt-master. However, applying the recommended fix by upgrading to a patched version is the most effective and comprehensive solution.

Conclusion

The vulnerability identified as CVE-2020-11651 in SaltStack Salt poses a significant security risk, allowing remote users to access certain methods without authentication. This can lead to unauthorized access, data breaches, and the execution of arbitrary commands on salt minions. It is crucial to upgrade to the recommended patched versions or implement network-level access controls to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for salt →

Share this vulnerability

FAQ

SaltStack Salt is an open-source configuration management and remote execution framework used for managing and automating large-scale computer systems.

Versions of SaltStack Salt before 2019.2.4 and 3000 before 3000.2 are affected by this vulnerability.

This vulnerability allows remote users to access certain methods without authentication, potentially leading to the retrieval of user tokens from the salt master and the execution of arbitrary commands on salt minions. This can result in unauthorized access, data breaches, and the compromise of affected systems.

To fix this vulnerability, it is recommended to upgrade to SaltStack Salt version 2019.2.4 or later, or 3000.2 or later. These versions include the necessary fixes to properly validate method calls and prevent unauthorized access.

As a temporary workaround, users can implement network-level access controls to restrict access to the salt-master process. This can be achieved by configuring firewalls or other network security measures to only allow trusted sources to communicate with the salt-master. However, upgrading to a patched version is the most effective solution.

Related vulnerabilities

Recent vulnerabilities recorded for salt.

How To Fix

Latest published version: 3008.3.0 as of 22 Oct 2026

pip install --upgrade "salt==3008.3.0"

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 2019.2.4 2019.2.4
    pip install --upgrade "salt==2019.2.4"
  • >= 3000, < 3000.2 3000.2
    pip install --upgrade "salt==3000.2"

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback