Salt vulnerable to Improper Certificate Validation

published 2017-08-25 9 y ago modified 2026-06-17 4 mo ago also GHSA-8j9g-c9rp-jvg4 , PYSEC-2017-31 , EUVD-2017-0115

cvss: 7.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

Salt before 2014.7.6 does not verify certificates when connecting via the aliyun, proxmox, and splunk modules.

Patch / fix

fixed in 1 links 3

pypi salt 2014.7.6

docs.saltstack.com/en/latest/topics/releases/2014.7.6.html advisory
openwall.com/lists/oss-security/2015/05/19/2 advisory
bugzilla.redhat.com/show_bug.cgi?id=1222960 advisory

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-4017 updated 2026-05-13 cvss 4.3

salt: Certificates are not verified when connecting to server with certain modules

Red Hat Ceph Storage 1.2 salt Red Hat Ceph Storage 1.3 salt
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

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

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
pypi	salt	<2014.7.6	2014.7.6

Classification

Weakness

CWE-295 Improper Certificate Validation

References

docs.saltstack.com /en/latest/topics/releases/2014.7.6.html
web, patch, release-notes, vendor-advisory
openwall.com /lists/oss-security/2015/05/19/2
mailing-list, web, patch, third-party-advisory
bugzilla.redhat.com /show_bug.cgi?id=1222960
web, issue-tracking, patch, third-party-advisory, report
groups.google.com /forum/#%21topic/salt-users/8Kv1bytGD6c
nvd.nist.gov /vuln/detail/CVE-2015-4017
advisory
github.com /pypa/advisory-database/tree/main/vulns/salt/PYSEC-2017-31.yaml
web
github.com /saltstack/salt
package
groups.google.com /forum/#!topic/salt-users/8Kv1bytGD6c
web
github.com /advisories/GHSA-8j9g-c9rp-jvg4
advisory

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.

Summary