salt: Jinja renderer does not protect against server-side template injection attacks

An issue was discovered in through SaltStack Salt before 3002.5. The jinja renderer does not protect against server side template injection attacks.

salt: Directory traversal in wheel.pillar_roots.write

An issue was discovered in through SaltStack Salt before 3002.5. The salt.wheel.pillar_roots.write method is vulnerable to directory traversal.

salt: API does not honor eAuth credentials for the wheel_async client

An issue was discovered in through SaltStack Salt before 3002.5. salt-api does not honor eauth credentials for the wheel_async client. Thus, an attacker can remotely run any wheel modules on the master.

salt: allows malacious actor to subvert the proper behaviour of the given minion software

An issue was discovered in SaltStack Salt before 3003.3. The salt minion installer will accept and use a minion config file at C:\salt\conf if that file is in place before the installer is run. This allows for a malicious actor to subvert the proper behaviour of the given minion software.

salt: user having control of source and source_hash URLs leads to root access

An issue was discovered in SaltStack Salt before 3003.3. A user who has control of the source, and source_hash URLs can gain full file system access as root on a salt minion.

salt: Certain modules do not always validated SSL certificates

In SaltStack Salt before 3002.5, when authenticating to services using certain modules, the SSL certificate is not always validated.

salt: Authentication to vCenter, vSphere, and ESXi servers does not always validate the SSL/TLS certificate

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.

salt: Privilege escalation on a minion when an unprivileged user is able to create files in any non-blacklisted directory

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.

salt: salt-netapi improperly validates eauth credentials and tokens

In SaltStack Salt through 3002, salt-netapi improperly validates eauth credentials and tokens. A user can bypass authentication and invoke Salt SSH.

salt: creates certificates with weak file permissions

The TLS module within SaltStack Salt through 3002 creates certificates with weak file permissions.

salt: salt-api NET API with the ssh client enabled is vulnerable to command injection

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.

SaltStack Salt 2018.3, 2019.2 is affected by: SQL Injection. The impact is: An attacker could escalate privileges on MySQL server deployed by cloud provider. It leads to RCE. The component is: The mysql.user_chpass function from the MySQL module for Salt. The attack vector is: specially crafted password string. The fixed version is: 2018.3.4.

salt: Remote command execution and incorrect access control when using salt-api

SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allow remote attackers to bypass authentication and execute arbitrary commands via salt-api(netapi).

salt: Directory traversal in salt-api allows remote attackers to identitfy arbitrary files

Directory Traversal vulnerability in salt-api in SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allows remote attackers to determine which files exist on the server.

salt: Compromised salt-minions can impersonate the salt-master

In SaltStack Salt before 2016.3.6, compromised salt-minions can impersonate the salt-master.

SaltStack RSA Key Generation allows remote users to decrypt communications