ID CVE-2018-15751
Summary 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).
References
Vulnerable Configurations
  • SaltStack Salt 0.6.0
    cpe:2.3:a:saltstack:salt:0.6.0
  • SaltStack Salt 0.7.0
    cpe:2.3:a:saltstack:salt:0.7.0
  • SaltStack Salt 0.8.0
    cpe:2.3:a:saltstack:salt:0.8.0
  • SaltStack Salt 0.8.7
    cpe:2.3:a:saltstack:salt:0.8.7
  • SaltStack Salt 0.8.8
    cpe:2.3:a:saltstack:salt:0.8.8
  • SaltStack Salt 0.8.9
    cpe:2.3:a:saltstack:salt:0.8.9
  • SaltStack Salt 0.9.0
    cpe:2.3:a:saltstack:salt:0.9.0
  • SaltStack Salt 0.9.2
    cpe:2.3:a:saltstack:salt:0.9.2
  • SaltStack Salt 0.9.3
    cpe:2.3:a:saltstack:salt:0.9.3
  • SaltStack Salt 0.9.4
    cpe:2.3:a:saltstack:salt:0.9.4
  • SaltStack Salt 0.9.5
    cpe:2.3:a:saltstack:salt:0.9.5
  • SaltStack Salt 0.9.6
    cpe:2.3:a:saltstack:salt:0.9.6
  • SaltStack Salt 0.9.7
    cpe:2.3:a:saltstack:salt:0.9.7
  • SaltStack Salt 0.9.8
    cpe:2.3:a:saltstack:salt:0.9.8
  • SaltStack Salt 0.9.9
    cpe:2.3:a:saltstack:salt:0.9.9
  • SaltStack Salt 0.10.0
    cpe:2.3:a:saltstack:salt:0.10.0
  • SaltStack Salt 0.10.2
    cpe:2.3:a:saltstack:salt:0.10.2
  • SaltStack Salt 0.10.3
    cpe:2.3:a:saltstack:salt:0.10.3
  • SaltStack Salt 0.10.4
    cpe:2.3:a:saltstack:salt:0.10.4
  • SaltStack Salt 0.10.5
    cpe:2.3:a:saltstack:salt:0.10.5
  • SaltStack Salt 0.11.0
    cpe:2.3:a:saltstack:salt:0.11.0
  • SaltStack Salt 0.12.0
    cpe:2.3:a:saltstack:salt:0.12.0
  • SaltStack Salt 0.13.0
    cpe:2.3:a:saltstack:salt:0.13.0
  • SaltStack Salt 0.14.0
    cpe:2.3:a:saltstack:salt:0.14.0
  • SaltStack Salt 0.15.0
    cpe:2.3:a:saltstack:salt:0.15.0
  • SaltStack Salt 0.15.1
    cpe:2.3:a:saltstack:salt:0.15.1
  • SaltStack Salt 0.16.0
    cpe:2.3:a:saltstack:salt:0.16.0
  • SaltStack Salt 0.16.2
    cpe:2.3:a:saltstack:salt:0.16.2
  • SaltStack Salt 0.16.3
    cpe:2.3:a:saltstack:salt:0.16.3
  • SaltStack Salt 0.16.4
    cpe:2.3:a:saltstack:salt:0.16.4
  • SaltStack Salt 0.17.0
    cpe:2.3:a:saltstack:salt:0.17.0
  • SaltStack Salt 0.17.1
    cpe:2.3:a:saltstack:salt:0.17.1
  • SaltStack Salt 2014.1.9
    cpe:2.3:a:saltstack:salt:2014.1.9
CVSS
Base: 7.5
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
nessus via4
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2018-1574.NASL
    description This update for salt fixes the following issues : - Crontab module fix: file attributes option missing (boo#1114824) - Fix git_pillar merging across multiple __env__ repositories (boo#1112874) - Bugfix: unable to detect os arch when RPM is not installed (boo#1114197) - Fix LDAP authentication issue when a valid token is generated by the salt-api even when invalid user credentials are passed. (U#48901) - Improved handling of LDAP group id. gid is no longer treated as a string, which could have lead to faulty group creations. (boo#1113784) - Fix remote command execution and incorrect access control when using salt-api. (boo#1113699) (CVE-2018-15751) - Fix Directory traversal vulnerability when using salt-api. Allows an attacker to determine what files exist on a server when querying /run or /events. (boo#1113698) (CVE-2018-15750) - Add multi-file support and globbing to the filetree (U#50018) - Bugfix: supportconfig non-root permission issues (U#50095) - Open profiles permissions to everyone for read-only - Preserving signature in 'module.run' state (U#50049) - Install default salt-support profiles - Remove unit test, came from a wrong branch. Fix merging failure. - Add CPE_NAME for osversion* grain parsing - Get os_family for RPM distros from the RPM macros - Install support profiles - Fix async call to process manager (boo#1110938) - Salt-based supportconfig implementation (technology preview) - Bugfix: any unicode string of length 16 will raise TypeError - Fix IPv6 scope (boo#1108557) - Handle zypper ZYPPER_EXIT_NO_REPOS exit code (boo#1108834, boo#1109893) - Bugfix for pkg_resources crash (boo#1104491) - Fix loosen azure sdk dependencies in azurearm cloud driver (boo#1107333) - Fix broken 'resolve_capabilities' on Python 3 (boo#1108995)
    last seen 2019-02-21
    modified 2019-01-28
    plugin id 119805
    published 2018-12-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=119805
    title openSUSE Security Update : salt (openSUSE-2018-1574)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2018-3815-1.NASL
    description This update for salt fixes the following issues : Security issues fixed : CVE-2018-15750: Fixed directory traversal vulnerability in salt-api (bsc#1113698). CVE-2018-15751: Fixed remote authentication bypass in salt-api(netapi) that allows to execute arbitrary commands (bsc#1113699). Non-security issues fixed: Improved handling of LDAP group id. gid is no longer treated as a string, which could have lead to faulty group creations (bsc#1113784). Fixed async call to process manager (bsc#1110938). Fixed OS arch detection when RPM is not installed (bsc#1114197). Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2019-01-28
    plugin id 120165
    published 2019-01-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=120165
    title SUSE SLED15 / SLES15 Security Update : salt (SUSE-SU-2018:3815-1)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2018-1569.NASL
    description This update for salt fixes the following issues : Security issues fixed : - CVE-2018-15750: Fixed directory traversal vulnerability in salt-api (bsc#1113698). - CVE-2018-15751: Fixed remote authentication bypass in salt-api(netapi) that allows to execute arbitrary commands (bsc#1113699). Non-security issues fixed : - Improved handling of LDAP group id. gid is no longer treated as a string, which could have lead to faulty group creations (bsc#1113784). - Fixed async call to process manager (bsc#1110938) - Fixed OS arch detection when RPM is not installed (bsc#1114197) - Crontab module fix: file attributes option missing (bsc#1114824) - Fix git_pillar merging across multiple __env__ repositories (bsc#1112874) This update was imported from the SUSE:SLE-15:Update update project.
    last seen 2019-02-21
    modified 2019-01-28
    plugin id 119759
    published 2018-12-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=119759
    title openSUSE Security Update : salt (openSUSE-2018-1569)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_4F7C6AF36A2C4EAD845304E509688D45.NASL
    description SaltStack reports : Remote command execution and incorrect access control when using salt-api. Directory traversal vulnerability when using salt-api. Allows an attacker to determine what files exist on a server when querying /run or /events.
    last seen 2019-02-21
    modified 2019-01-28
    plugin id 118477
    published 2018-10-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=118477
    title FreeBSD : salt -- multiple vulnerabilities (4f7c6af3-6a2c-4ead-8453-04e509688d45)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2018-3813-1.NASL
    description This update for salt fixes the following issues : Salt was updated to version 2016.11.10 and contains the following fixes : Security issues fixed : CVE-2018-15750: Fixed directory traversal vulnerability in salt-api (bsc#1113698). CVE-2018-15751: Fixed remote authentication bypass in salt-api(netapi) that allows to execute arbitrary commands (bsc#1113699). Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2019-01-28
    plugin id 119115
    published 2018-11-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=119115
    title SUSE SLES11 Security Update : salt (SUSE-SU-2018:3813-1)
refmap via4
confirm
mlist
  • [salt-users] 20181024 2017.7.8 Released - Security Advisory
  • [salt-users] 20181024 2018.3.3 Released - Security Advisory
Last major update 24-10-2018 - 18:29
Published 24-10-2018 - 18:29
Last modified 25-01-2019 - 10:04
Back to Top