Skip to content

Vendor

saltstack vulnerabilities

30 published CVES affecting saltstack, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
30
Critical
9
High
12
Medium
8
Low
1
Unscored
0
CISA KEV
2
Atom feed of saltstack alerts

Products

Latest saltstack CVEs

Newest publication first · page 1 of 2

  1. CriticalCVSS 9.8 EPSS 96.6% CISA KEV added 2021-11-03 Exploited in the wild Framework module Public exploit

    An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2. The salt-master process ClearFuncs class does not properly validate method calls. This allows a remote user to access some methods without authentication. These methods can be used to retrieve user...

  2. MediumCVSS 6.5 EPSS 86.4% CISA KEV added 2021-11-03 Exploited in the wild Framework module Public exploit

    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.

  3. CriticalCVSS 9.8

    In SaltStack Salt through 2019.2.0, the salt-api NET API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access to the API endpoint to execute arbitrary code on the salt-api host.

  4. HighCVSS 7.8

    The salt-ssh minion code in SaltStack Salt 2016.11 before 2016.11.4 copied over configuration from the Salt Master without adjusting permissions, which might leak credentials to local attackers on configured minions (clients).

  5. HighCVSS 8.1

    Salt 2015.8.x before 2015.8.4 does not properly handle clear messages on the minion, which allows man-in-the-middle attackers to execute arbitrary code by inserting packets into the minion-master data stream.

  6. HighCVSS 7.2

    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.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.