What is CVE-2020-35662?

CVE-2020-35662 is a high-severity security vulnerability in salt (pip), affecting versions < 2015.8.13. It is fixed in 2015.8.13, 2016.11.5, 2016.11.10, 2017.7.8, 2019.2.8, 3000.7, 3001.5, 3002.3.

How severe is CVE-2020-35662?

CVE-2020-35662 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of salt are affected by CVE-2020-35662?

salt (pip) versions < 2015.8.13 is affected.

Is CVE-2020-35662 exploitable, and should I be worried?

Whether CVE-2020-35662 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.

What actually determines whether CVE-2020-35662 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.

CVE-2020-35662 in salt | Intelligent Application Security

Q: How severe is CVE-2020-35662?

CVE-2020-35662 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of salt are affected by CVE-2020-35662?

salt (pip) versions < 2015.8.13 is affected.

Q: Is there a fix for CVE-2020-35662?

Yes. CVE-2020-35662 is fixed in 2015.8.13, 2016.11.5, 2016.11.10, 2017.7.8, 2019.2.8, 3000.7, 3001.5, 3002.3. Upgrade to this version or later.

Q: Is CVE-2020-35662 exploitable, and should I be worried?

Whether CVE-2020-35662 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.

Q: What actually determines whether CVE-2020-35662 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.

Q: How do I fix CVE-2020-35662?

Upgrade: salt to 2015.8.13 or later, salt to 2016.11.5 or later, salt to 2016.11.10 or later, salt to 2017.7.8 or later, salt to 2019.2.8 or later, salt to 3000.7 or later, salt to 3001.5 or later, salt to 3002.3 or later.

Summary

In SaltStack Salt before 3002.5, when authenticating to services using certain modules, the SSL certificate is not always validated.

Impact

CVE-2020-35662 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2015.8.13, 2016.11.5, 2016.11.10, 2017.7.8, 2019.2.8, 3000.7, 3001.5, 3002.3); upgrading removes the vulnerable code path.

Affected versions

salt (< 2015.8.13) salt (>= 2016.3.0, < 2016.11.5) salt (>= 2016.11.7, < 2016.11.10) salt (>= 2017.5.0, < 2017.7.8) salt (>= 2018.2.0, <= 2018.3.5) salt (>= 2019.2.0, < 2019.2.8) salt (>= 3000, < 3000.7) salt (>= 3001, < 3001.5) salt (>= 3002, < 3002.3)

Security releases

salt → 2015.8.13 (pip) salt → 2016.11.5 (pip) salt → 2016.11.10 (pip) salt → 2017.7.8 (pip) salt → 2019.2.8 (pip) salt → 3000.7 (pip) salt → 3001.5 (pip) salt → 3002.3 (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 the following packages to resolve this vulnerability:

salt to 2015.8.13 or later; salt to 2016.11.5 or later; salt to 2016.11.10 or later; salt to 2017.7.8 or later; salt to 2019.2.8 or later; salt to 3000.7 or later; salt to 3001.5 or later; salt to 3002.3 or later

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

Frequently Asked Questions

What is CVE-2020-35662? CVE-2020-35662 is a high-severity security vulnerability in salt (pip), affecting versions < 2015.8.13. It is fixed in 2015.8.13, 2016.11.5, 2016.11.10, 2017.7.8, 2019.2.8, 3000.7, 3001.5, 3002.3.
How severe is CVE-2020-35662? CVE-2020-35662 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of salt are affected by CVE-2020-35662? salt (pip) versions < 2015.8.13 is affected.
Is there a fix for CVE-2020-35662? Yes. CVE-2020-35662 is fixed in 2015.8.13, 2016.11.5, 2016.11.10, 2017.7.8, 2019.2.8, 3000.7, 3001.5, 3002.3. Upgrade to this version or later.
Is CVE-2020-35662 exploitable, and should I be worried? Whether CVE-2020-35662 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
What actually determines whether CVE-2020-35662 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.
How do I fix CVE-2020-35662?
- Upgrade salt to 2015.8.13 or later
- Upgrade salt to 2016.11.5 or later
- Upgrade salt to 2016.11.10 or later
- Upgrade salt to 2017.7.8 or later
- Upgrade salt to 2019.2.8 or later
- Upgrade salt to 3000.7 or later
- Upgrade salt to 3001.5 or later
- Upgrade salt to 3002.3 or later

Other vulnerabilities in salt

CVE-IDSeverityPackage summary

CVE-2025-62349Highsalt: Salt Authentication Protocol Version Downgrade Allows Minion Impersonation CVE-2025-62348Highsalt: Salt junos Module Vulnerable to Code Injection via Specially Crafted YAML Payload CVE-2024-38824Criticalsalt: Salt vulnerable to directory traversal attack in file receiving method CVE-2025-22242Mediumsalt: Salt's worker process vulnerable to denial of service through file read operation CVE-2025-22238Mediumsalt: Salt vulnerable to directory traversal attack in minion file cache creation

Summary

Impact

Affected versions

Security releases

Kodem intelligence

Remediation advice

Frequently Asked Questions

Other vulnerabilities in salt

Other vulnerabilities in salt

Stop the waste.Protect your environment with Kodem.

Stop the waste.
Protect your environment with Kodem.