CVE-2023-20898: Vulnerability in salt package

salt Updated 02 Oct 2025

Summary

05/09/2023

Disclosed on

CVE-2023-20898

CVE

Yes i

Fix available

Moderate

Severity

7.8

CVSS Score

CVE-2023-20898: Git Providers can read from the wrong environment because they get the same cache directory base name in Salt masters prior to 3005.2 or 3006.2. Affects salt across 2 version ranges.

< 3005.2 >= 3006.0, < 3006.2

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

Also tracked for

salt · Debian:10

The same CVE-2023-20898 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

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 Browse

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.

Background

The salt package is a popular open-source configuration management and remote execution tool. It is widely used for managing and automating infrastructure. Salt masters prior to versions 3005.2 or 3006.2 are susceptible to a vulnerability that allows Git Providers to read from the wrong environment. This occurs due to the same cache directory base name being used for different environments. As a result, there is a risk of wrongful data disclosure, wrongful executions, data corruption, and crashes.

Vulnerability Detail

The vulnerability in the salt package allows Git Providers to access incorrect or garbage data from the cache directory. This can lead to various security issues, including data disclosure, execution of unintended actions, data corruption, and system crashes. The vulnerability arises when different environments are used with Git Providers, as they all share the same cache directory base name. Attackers can exploit this vulnerability to gain unauthorized access to sensitive data or manipulate the system in unintended ways.

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.

< 3005.2 3005.2
```
pip install --upgrade "salt==3005.2"
```
>= 3006.0, < 3006.2 3006.2
```
pip install --upgrade "salt==3006.2"
```

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

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended solution is to upgrade to the fixed versions of Salt masters.

Conclusion

The vulnerability in the salt package allows Git Providers to read from the wrong environment, leading to potential data disclosure, wrongful executions, data corruption, and crashes. It is crucial to upgrade to the fixed versions of Salt masters (3006.2 or 3005.2) to mitigate these risks. Additionally, users can utilize the Vulert Playground at https://vulert.com/scanner to check if their system is affected by this vulnerability. For further support and assistance, please reach out to DevNack.com.

See every vulnerability recorded for salt →

FAQ

What is the impact of this vulnerability?

The vulnerability can result in wrongful data disclosure, wrongful executions, data corruption, and system crashes. Attackers can exploit this vulnerability to gain unauthorized access to sensitive data or manipulate the system in unintended ways.

How can I check if my system is affected?

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply provide your Pipfile.lock file, and Vulert will analyze it for any open-source vulnerabilities, including this specific issue.

Are there any known exploits for this vulnerability?

At the time of this report, there are no known public exploits for this vulnerability. However, it is crucial to apply the recommended fix to mitigate any potential risks.

Can this vulnerability be exploited remotely?

Yes, this vulnerability can be exploited remotely if the affected Salt masters are accessible over the network. Attackers can potentially exploit this vulnerability to gain unauthorized access or manipulate the system remotely.