Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI

CVE-2020-35662

HIGH

CVE-2020-35662 is a high-severity (CVSS 7.4) CWE-295 vulnerability in salt. O3 Security confirms whether CVE-2020-35662 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SaltStack Salt Improper SSL Certificate Validation

Also known asGHSA-qx72-q6w3-qgc7PYSEC-2021-75
Published
Feb 27, 2021
Updated
Jul 8, 2026
Affected
9 pkgs
Patched
8 / 9
Exploits
None indexed

Blast Radius

9 pkgs affected
🐍salt🐍salt🐍salt🐍salt🐍salt🐍salt🐍salt🐍salt+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

9 total 8 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIsaltall versions2015.8.13
🐍PyPIsalt2016.3.0&&< 2016.11.52016.11.5
🐍PyPIsalt2016.11.7&&< 2016.11.102016.11.10
🐍PyPIsalt2017.5.0&&< 2017.7.82017.7.8
🐍PyPIsalt2018.2.0No fix
🐍PyPIsalt2019.2.0&&< 2019.2.82019.2.8

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for salt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update salt to 2015.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-35662 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-35662 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-35662. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In SaltStack Salt before 3002.5, when authenticating to services using certain modules, the SSL certificate is not always validated.
O3 Security · Impact-Aware SCA

Is CVE-2020-35662 in your dependencies?

O3 detects CVE-2020-35662 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.