CVE-2013-4437

CVE-2013-4437 is a high-severity security vulnerability in salt (pip), affecting versions = 0.17.0. It is fixed in 0.17.1.

Summary

Unspecified vulnerability in salt-ssh in Salt (aka SaltStack) 0.17.0 has unspecified impact and vectors related to "insecure Usage of /tmp."

Impact

Affected versions

salt (= 0.17.0)

Security releases

salt → 0.17.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade salt to 0.17.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2013-4437? CVE-2013-4437 is a high-severity security vulnerability in salt (pip), affecting versions = 0.17.0. It is fixed in 0.17.1.
  2. Which versions of salt are affected by CVE-2013-4437? salt (pip) versions = 0.17.0 is affected.
  3. Is there a fix for CVE-2013-4437? Yes. CVE-2013-4437 is fixed in 0.17.1. Upgrade to this version or later.
  4. Is CVE-2013-4437 exploitable, and should I be worried? Whether CVE-2013-4437 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2013-4437 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2013-4437? Upgrade salt to 0.17.1 or later.

Other vulnerabilities in salt

CVE-2025-62349CVE-2025-62348CVE-2024-38824CVE-2025-22242CVE-2025-22238

Stop the waste.
Protect your environment with Kodem.