Advisories for Pypi/Salt package

A specially crafted url can be created which leads to a directory traversal in the salt file server. A malicious user can read an arbitrary file from a Salt master’s filesystem.

Syndic cache directory creation is vulnerable to a directory traversal attack in salt project which can lead a malicious attacker to create an arbitrary directory on a Salt master.

Salt masters prior to 3005.2 or 3006.2 contain a DoS in minion return. After receiving several bad packets on the request server equal to the number of worker threads, the master will become unresponsive to return requests until restarted.

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. Anything that uses Git Providers with different environments can get garbage data or the wrong data, which can lead to wrongful data disclosure, wrongful executions, data corruption and/or crash.

Buffer Overflow vulnerability in Saltstack v.3003 and before allows attacker to execute arbitrary code via the func variable in salt/salt/modules/status.py file.

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.

modules/serverdensity_device.py in SaltStack before 2014.7.4 does not properly handle files in /tmp.

Salt (aka SaltStack) before 0.15.0 through 0.17.0 allows remote authenticated minions to impersonate arbitrary minions via a crafted minion with a valid key.

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 …

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.

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.

An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. Job publishes and file server replies are susceptible to replay attacks, which can result in an attacker replaying job publishes causing minions to run old jobs. File server replies can also be re-played. A sufficient craft attacker could gain root access on minion under certain scenarios.

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.

An issue was discovered in SaltStack Salt 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.

In SaltStack Salt, a command injection vulnerability exists in the snapper module that allows for local privilege escalation on a minion. The attack requires that a file is created with a pathname that is backed up by snapper, and that the master calls the snapper.diff function (which executes popen unsafely).

A Incorrect Implementation of Authentication Algorithm vulnerability allows local attackers to execute arbitrary code via salt without the need to specify valid credentials.

An issue was discovered in SaltStack Salt's salt.wheel.pillar_roots.write method which is vulnerable to directory traversal.

In SaltStack Salt, eauth tokens can be used once after expiration. They might be used to run command against the salt master or minions.

An issue was discovered in SaltStack's salt-api. The salt-api ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options provided in an API request.

In SaltStack Salt, authentication to VMware vcenter, vsphere, and esxi servers (in the vmware.py files) does not always validate the SSL/TLS certificate.

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

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

An issue was discovered in SaltStack Salt. 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-ignored directory.

An issue was discovered in SaltStack Salt. By sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.

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

An issue was discovered in SaltStack Salt's salt.modules.cmdmod due to logging credentials at the info or error log level.

An issue was discovered in SaltStack Salt Sending crafted web requests to the Salt API, with the SSH client enabled, can result in shell injection.

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

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

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.

The salt-master process ClearFuncs class allows access to some methods that improperly sanitize paths. These methods allow arbitrary directory access to authenticated users.

In SaltStack Salt, 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 is affected by SQL Injection. Through a specially crafted password string, an attacker could escalate privileges on MySQL server deployed by cloud provider leading to RCE.

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

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

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

A Directory traversal vulnerability in minion id validation in SaltStack Salt allows remote minions with incorrect credentials to authenticate to a master via a crafted minion ID.

SaltStack Salt allows remote attackers to cause a denial of service via a crafted authentication request.

When using the local_batch client from salt-api in SaltStack Salt, external authentication is not respected, enabling all authentication to be bypassed.

Salt-api in SaltStack Salt allows arbitrary command execution on a salt-master via Salt's ssh_client.

A directory traversal vulnerability in minion id validation in SaltStack Salt allows remote minions with incorrect credentials to authenticate to a master via a crafted minion ID.

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

Salt 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.

Salt contains a flaw in seed.py, salt-ssh, and salt-cloud that is due to the program creating temporary files insecurely. This may allow a local attacker to have an unspecified impact.