Skip to content
Fencer Intel
high 8.8

CVE-2017-5192 json

SaltStack Salt Authentication Bypass when using the local_batch client from salt-api

published 2017-09-26 9 y ago modified 2026-06-17 4 mo ago also GHSA-f2h7-4f84-8qrm , PYSEC-2017-38 , EUVD-2017-0122

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

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.

Patch / fix

  • pypi salt 2015.8.13, 2016.3.5, 2016.11.2
  • salt Alpine 3.5 2016.11.2-r0

alpine advisories ALPINE-CVE-2017-5192

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-5192 updated cvss 7.5

salt: local_batch client external authentication not respected

  • Red Hat Ceph Storage 1.3 salt Red Hat Ceph Storage 2 salt, salt-minion Red Hat Storage Console 2 salt
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.73% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi salt
<2015.8.13
>=2016.3.0, <2016.3.5
>=2016.11.0, <2016.11.2
>=2016.3, <2016.3.5
>=2016.11, <2016.11.2
2015.8.13
2016.3.5
2016.11.2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.