What is CVE-2017-5192?

CVE-2017-5192 is a high-severity improper authentication vulnerability in salt (pip), affecting versions < 2015.8.13. It is fixed in 2015.8.13, 2016.3.5, 2016.11.2. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2017-5192?

CVE-2017-5192 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of salt are affected by CVE-2017-5192?

salt (pip) versions < 2015.8.13 is affected.

Is there a fix for CVE-2017-5192?

Yes. CVE-2017-5192 is fixed in 2015.8.13, 2016.3.5, 2016.11.2. Upgrade to this version or later.

Is CVE-2017-5192 exploitable, and should I be worried?

Whether CVE-2017-5192 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-5192 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-5192 in salt | Intelligent Application Security

Q: How severe is CVE-2017-5192?

CVE-2017-5192 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of salt are affected by CVE-2017-5192?

salt (pip) versions < 2015.8.13 is affected.

Q: Is there a fix for CVE-2017-5192?

Yes. CVE-2017-5192 is fixed in 2015.8.13, 2016.3.5, 2016.11.2. Upgrade to this version or later.

Q: Is CVE-2017-5192 exploitable, and should I be worried?

Whether CVE-2017-5192 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-5192 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-5192?

Upgrade: salt to 2015.8.13 or later, salt to 2016.3.5 or later, salt to 2016.11.2 or later.

Summary

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.

Impact

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2017-5192 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2015.8.13, 2016.3.5, 2016.11.2); upgrading removes the vulnerable code path.

Affected versions

salt (< 2015.8.13) salt (>= 2016.3.0, < 2016.3.5) salt (>= 2016.11.0, < 2016.11.2)

Security releases

salt → 2015.8.13 (pip) salt → 2016.3.5 (pip) salt → 2016.11.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

salt to 2015.8.13 or later; salt to 2016.3.5 or later; salt to 2016.11.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-5192? CVE-2017-5192 is a high-severity improper authentication vulnerability in salt (pip), affecting versions < 2015.8.13. It is fixed in 2015.8.13, 2016.3.5, 2016.11.2. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2017-5192? CVE-2017-5192 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of salt are affected by CVE-2017-5192? salt (pip) versions < 2015.8.13 is affected.
Is there a fix for CVE-2017-5192? Yes. CVE-2017-5192 is fixed in 2015.8.13, 2016.3.5, 2016.11.2. Upgrade to this version or later.
Is CVE-2017-5192 exploitable, and should I be worried? Whether CVE-2017-5192 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-5192 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-5192?
- Upgrade salt to 2015.8.13 or later
- Upgrade salt to 2016.3.5 or later
- Upgrade salt to 2016.11.2 or later

Other vulnerabilities in salt

CVE-2025-62349 CVE-2025-62348 CVE-2024-38824 CVE-2025-22242 CVE-2025-22238