Saltstack Salt vulnerabilities, page 2
53 vulnerabilities
Known vulnerabilities in Saltstack Salt, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2015-1839ubuntusalt+3
EPSS score0.43%
modules/chef.py in SaltStack before 2014.7.4 does not properly handle files in /tmp.CVE-2015-1838ubuntusalt+3EPSS score0.43%
modules/serverdensity_device.py in SaltStack before 2014.7.4 does not properly handle files in /tmp.CVE-2015-4017ubuntusalt+2EPSS score1.06%
Salt before 2014.7.6 does not verify certificates when connecting via the aliyun, proxmox, and splunk modules.CVE-2015-8034ubuntusalt+5EPSS score0.41%
The state.sls function in Salt before 2015.8.3 uses weak permissions on the cache data, which allows local users to obtain sensitive information by reading the file.CVE-2016-1866ubuntusalt+3EPSS score1.52%
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.CVE-2016-9639ubuntusalt+16EPSS score2.60%
Salt before 2015.8.11 allows deleted minions to read or write to minions with the same id, related to caching.CVE-2016-3176ubuntusalt+5EPSS score0.87%
Salt before 2015.5.10 and 2015.8.x before 2015.8.8, when PAM external authentication is enabled, allows attackers to bypass the configured authentication service by passing an alternate service with a command sent to LocalClient.CVE-2020-16846ubuntusalt+5KEVEPSS score99.59%
An issue was discovered in SaltStack Salt through 3002. Sending crafted web requests to the Salt API, with the SSH client enabled, can result in shell injection.CVE-2020-11651canonicalubuntu_linux+6KEVEPSS score96.61%
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 tokens from the salt master and/or run arbitrary commands on salt minions.CVE-2020-11652blackberryworkspaces_server+7KEVEPSS score86.18%
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.CVE-2020-17490ubuntusalt+3EPSS score0.42%
The TLS module within SaltStack Salt through 3002 creates certificates with weak file permissions.CVE-2020-25592ubuntusalt+3EPSS score56.82%
In SaltStack Salt through 3002, salt-netapi improperly validates eauth credentials and tokens. A user can bypass authentication and invoke Salt SSH.CVE-2020-28972ubuntusalt+4EPSS score3.08%
In SaltStack Salt before 3002.5, authentication to VMware vcenter, vsphere, and esxi servers (in the vmware.py files) does not always validate the SSL/TLS certificate.CVE-2020-28243ubuntusalt+4EPSS score4.30%
An issue was discovered in SaltStack Salt before 3002.5. The minion's restartcheck is vulnerable to command injection via a crafted process name. This allows for a local privilege escalation by any user able to create a files on the minion in a non-blacklisted directory.CVE-2020-35662ubuntusalt+4EPSS score2.96%
In SaltStack Salt before 3002.5, when authenticating to services using certain modules, the SSL certificate is not always validated.CVE-2014-3563ubuntusalt+2EPSS score0.41%
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.CVE-2022-22935ubuntusalt+2EPSS score1.62%
An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. A minion authentication denial of service can cause a MiTM attacker to force a minion process to stop by impersonating a master.CVE-2022-22967ubuntusalt+38EPSS score2.06%
An issue was discovered in SaltStack Salt in versions before 3002.9, 3003.5, 3004.2. PAM auth fails to reject locked accounts, which allows a previously authorized user whose account is locked still run Salt commands when their account is locked. This affects both local shell accounts with an active session and salt-api users that authenticate via PAM eauth.CVE-2022-22941ubuntusalt+2EPSS score1.34%
An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. When configured as a Master-of-Masters, with a publisher_acl, if a user configured in the publisher_acl targets any minion connected to the Syndic, the Salt Master incorrectly interpreted no valid targets as valid, allowing configured users to target any of the minions connected to the syndic with their configured commands. This requires a syndic master combined with publisher_acl configured on the Master-of-Masters, allowing users specified in the publisher_acl to bypass permissions, publishing authorized commands to any configured minion.CVE-2022-22934ubuntusalt+2EPSS score0.88%
An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. Salt Masters do not sign pillar data with the minion’s public key, which can result in attackers substituting arbitrary pillar data.