Skip to content
Fencer Intel
low 3.3

CVE-2015-8034 json

Salt uses weak permissions on the cache data

published 2017-01-30 9 y ago modified 2026-06-17 4 mo ago also GHSA-6prw-8xhm-h247 , PYSEC-2017-32 , EUVD-2017-0116

cvss
3.3
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 34%
public exploits
0
none known

Summary

The state.sls function in Salt before 2015.8.3 uses weak permissions on the cache data, which allows local users to obtain sensitive information by reading the file.

Patch / fix

  • pypi salt 2015.8.3
  • salt Ubuntu Pro 14.04 LTS 0.17.5+ds-1ubuntu0.1~esm5

ubuntu advisories UBUNTU-CVE-2015-8034

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • salt Enterprise Storage 2.1, Enterprise Storage 1.0 2014.1.10-8.4
  • salt Enterprise Storage 2 2014.1.10-6.4

suse advisories SUSE-SU-2016:1896-1SUSE-SU-2016:1895-1SUSE-SU-2016:1897-1

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-2015-8034 updated cvss 4.0

salt: Information leak from state.sls cache data stored as world-readable

  • Red Hat Ceph Storage 1.2 salt, calamari-server Red Hat Ceph Storage 1.3 salt, calamari-server
    affected: no fix planned “Will not fix”

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.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi salt
<2015.8.3
2015.8.3

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.