Skip to content
Fencer Intel
high 7.8

CVE-2017-8109 json

SaltStack Salt Information Exposure

published 9y ago modified 4mo ago also GHSA-xcx4-5wq7-g5g7 , PYSEC-2017-82 , EUVD-2017-0126

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

Summary

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

Patch / fix

  • pypi salt 2016.11.4
  • salt SLE Point of Sale 12 SP2, SLE Module for Advanced Systems Management 12, Manager Server 3.0 +4 more 2016.11.4-45.2
  • salt SLES 11 SP4-CLIENT-TOOLS, SLES 11 SP3-CLIENT-TOOLS 2016.11.4-42.2

suse advisories SUSE-SU-2017:1582-1SUSE-SU-2017:1581-1

Is CVE-2017-8109 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-8109 updated cvss 5.5

salt: Minion code copies over configuration from the Salt Master without adjusting permissions

  • 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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi salt
>=2016.11, <2016.11.4
2016.11.4

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.