Vulnerability in Salt Package (CVE-2023-20898)

salt Updated 02 Oct 2025

Summary

04/06/2024
N/A
No i
High
7.8

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 versions < c71ff9204ab5ae90b21b68cf3447be472a8db8f2. No fix is published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Salt package is a popular configuration management and remote execution tool used in various environments. It allows administrators to manage and automate the configuration of multiple systems. The package is widely used in Debian 10 ecosystem. However, prior to versions 3005.2 or 3006.2, Salt masters are susceptible to a vulnerability that can result in data disclosure, wrongful executions, data corruption, and crashes.

Vulnerability Detail

The vulnerability (CVE-2023-20898) arises from the fact that Git Providers in Salt masters prior to versions 3005.2 or 3006.2 can read from the wrong environment due to the same cache directory base name. This can lead to the retrieval of incorrect or garbage data, which can have severe consequences. Attackers could exploit this vulnerability to gain unauthorized access to sensitive information, execute malicious code, corrupt data, or cause system crashes.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update the Salt package to the fixed versions mentioned above.

Conclusion

The vulnerability in the Salt package (CVE-2023-20898) can have severe consequences, including data disclosure, wrongful executions, data corruption, and crashes. It is crucial for users to update their Salt installations to versions 3005.2 or 3006.2 or later 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

The vulnerability can result in wrongful data disclosure, wrongful executions, data corruption, and system crashes. Attackers could exploit this vulnerability to gain unauthorized access to sensitive information or execute malicious code.

Salt masters prior to versions 3005.2 or 3006.2 are affected by this vulnerability.

No, there is no known workaround. Updating to the fixed versions is the recommended solution.

There are no known instances of this vulnerability being exploited in the wild at this time.

You can find more information about this vulnerability in the CVE-2023-20898 JSON report available at the following source: https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-20898.json

Related vulnerabilities

Recent vulnerabilities recorded for salt.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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