# CVE-2017-5192: SaltStack Salt Authentication Bypass when using the local_batch client from salt-api

> Attackers can bypass authentication in SaltStack Salt's local_batch client via salt-api, gaining unauthorized access to the system.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f2h7-4f84-8qrm, PYSEC-2017-38, UBUNTU-CVE-2017-5192

## What is CVE-2017-5192?

CVE-2017-5192 is a high-severity authentication bypass vulnerability in Saltstack Salt, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When using the local_batch client from salt-api in SaltStack Salt before 2015.8.13, 2016.3.x before 2016.3.5, and 2016.11.x before 2016.11.2, external authentication is not respected, enabling all authentication to be bypassed.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-5192?

7 open source packages ship an affected version, including salt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `salt` | PyPI | All versions | 2015.8.13, 2016.3.5, 2016.11.2 |
| `salt` | PyPI | All versions | 2015.8.13 |
| `salt` | PyPI | All versions | 2015.8.13 |
| `salt` | PyPI | From 2016.11.0 | 2016.11.2 |
| `salt` | PyPI | From 2016.11.0 | 2016.11.2 |
| `salt` | PyPI | From 2016.3.0 | 2016.3.5 |
| `salt` | PyPI | From 2016.3.0 | 2016.3.5 |

Products: Saltstack Salt.

## How do I fix CVE-2017-5192?

Upgrade salt to a fixed version for your release line: 2015.8.13, 2016.3.5 or 2016.11.2.

## Is CVE-2017-5192 being exploited?

There is no known exploitation of CVE-2017-5192 in the wild and no public exploit code.

## Other vulnerabilities in Saltstack Salt

- [CVE-2013-4437](https://insights.sbomify.com/CVE-2013-4437/): SaltStack insecurely uses /tmp (critical 10.0)
- [CVE-2013-6617](https://insights.sbomify.com/CVE-2013-6617/): SaltStack Privilege Escalation vulnerability (critical 10.0)
- [CVE-2021-33226](https://insights.sbomify.com/CVE-2021-33226/): Code injection in n/a (critical 9.8)
- [CVE-2021-25315](https://insights.sbomify.com/CVE-2021-25315/): salt-api unauthenticated remote code execution (critical 9.8)
- [CVE-2018-15751](https://insights.sbomify.com/CVE-2018-15751/): SaltStack Salt Remote command execution and incorrect access control when using salt-api (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5192 and fix it if it is affected.

What it is: CVE-2017-5192 is a high-severity authentication bypass vulnerability in Saltstack Salt, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5192 in the wild and no public exploit code.

Affected packages and fixed versions:
- salt (PyPI): affected all versions; fixed in 2015.8.13, 2016.3.5, 2016.11.2
- salt (PyPI): affected all versions; fixed in 2015.8.13
- salt (PyPI): affected all versions; fixed in 2015.8.13
- salt (PyPI): affected from 2016.11.0; fixed in 2016.11.2
- salt (PyPI): affected from 2016.11.0; fixed in 2016.11.2
- salt (PyPI): affected from 2016.3.0; fixed in 2016.3.5
- salt (PyPI): affected from 2016.3.0; fixed in 2016.3.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5192/ (Markdown: https://insights.sbomify.com/CVE-2017-5192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5192
- OSV: https://osv.dev/vulnerability/CVE-2017-5192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5192/
Summaries are generated and may contain mistakes; the official description above is the record.