Skip to content
Noroxi
CVE-2020-28972· NVD / CVE Program· CNA mitre

In SaltStack Salt before 3002.5, authentication to VMware vcenter, vsphere, and esxi servers (in the vmware.py files) does not always valida

In SaltStack Salt before 3002.5, authentication to VMware vcenter, vsphere, and esxi servers (in the vmware.py files) does not always validate the SSL/TLS certificate.

MediumCVSS 5.9 · v3.1—No exploit Fix available
Published
Feb 27, 2021
Updated
Jun 16, 2026
EPSS
3.1% · 87th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.1%

Affected systems

VendorProduct
saltstacksalt
fedoraprojectfedora
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • debian debian linux11.0
  • debian debian linux9.0
  • fedoraproject fedora32
  • fedoraproject fedora33
  • fedoraproject fedora34
  • saltstack salt2016.11.4 and later · before 2016.11.5
  • saltstack salt2016.11.7 and later · before 2016.11.10
  • saltstack salt2017.5.0 and later · before 2017.7.8
  • saltstack salt2018.2.0 and later · up to 2018.3.5 inclusive
  • saltstack saltbefore 2015.8.10
  • saltstack salt2019.2.6 and later · before 2019.2.8
  • saltstack salt3000 and later · before 3000.6
  • saltstack salt3001 and later · before 3001.4
  • saltstack salt3002 and later · before 3002.5
  • saltstack salt2019.2.0 and later · before 2019.2.5
  • saltstack salt2015.8.11 and later · before 2015.8.13
  • saltstack salt2016.3.0 and later · before 2016.3.4
  • saltstack salt2016.3.5 and later · before 2016.3.6
  • saltstack salt2016.3.7 and later · before 2016.3.8

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:9saltbefore 2016.11.2+ds-1+deb9u72016.11.2+ds-1+deb9u7
openSUSE:Leap 15.2saltbefore 3000-lp152.3.27.13000-lp152.3.27.1
PyPIsaltfrom 2015.8.11 · before 2015.8.132015.8.13
PyPIsaltfrom 2016.11.0 · before 2016.11.32016.11.3
PyPIsaltfrom 2016.11.4 · before 2016.11.52016.11.5
PyPIsaltfrom 2016.11.7 · before 2016.11.102016.11.10
PyPIsaltfrom 2016.3.0 · before 2016.3.42016.3.4
PyPIsaltfrom 2016.3.0 · before 2016.11.52016.11.5
PyPIsaltfrom 2016.3.5 · before 2016.3.62016.3.6
PyPIsaltfrom 2016.3.7 · before 2016.3.82016.3.8
PyPIsaltfrom 2017.5.0 · before 2017.7.82017.7.8
PyPIsaltfrom 2017.7.0 · before 2017.7.82017.7.8
PyPIsaltfrom 2018.2.0 · up to and including 2018.3.5—
PyPIsaltfrom 2018.3.0rc1 · before 2019.2.0rc12019.2.0rc1
PyPIsaltfrom 2019.2.0 · before 2019.2.52019.2.5
PyPIsaltfrom 2019.2.0 · before 2019.2.82019.2.8
PyPIsaltfrom 2019.2.6 · before 2019.2.82019.2.8
PyPIsaltfrom 3000 · before 3000.73000.7
PyPIsaltfrom 3000 · before 3000.63000.6
PyPIsaltfrom 3001 · before 3001.53001.5
PyPIsaltfrom 3001 · before 3001.43001.4
PyPIsaltfrom 3002 · before 3002.53002.5
PyPIsaltfrom 3002 · before 3002.33002.3
PyPIsaltbefore 2015.8.102015.8.10

+11

Other highest-scoring records for the same primary product.

  • CVE-2020-16846An issue was discovered in SaltStack Salt through 3002.KEV
    99Now
  • CVE-2020-11651An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV
    98Now
  • CVE-2020-11652An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV
    82Now
  • CVE-2021-25282An issue was discovered in through SaltStack Salt before 3002.5.
    64This week
  • CVE-2021-3197An issue was discovered in SaltStack Salt before 3002.5.
    61This week
  • CVE-2021-25281An issue was discovered in through SaltStack Salt before 3002.5.
    61This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:salt2016.11.2+ds-1+deb9u7 · Debian:9Package registry (OSV)
opensuse:salt3000-lp152.3.27.1 · openSUSE:Leap 15.2Package registry (OSV)
PyPI:salt2015.8.10Package registry (OSV)
PyPI:salt2015.8.13Package registry (OSV)
PyPI:salt2016.11.10Package registry (OSV)
PyPI:salt2016.11.3Package registry (OSV)
PyPI:salt2016.11.5Package registry (OSV)
PyPI:salt2016.3.4Package registry (OSV)
PyPI:salt2016.3.6Package registry (OSV)
PyPI:salt2016.3.8Package registry (OSV)
PyPI:salt2017.7.8Package registry (OSV)
PyPI:salt2019.2.0rc1Package registry (OSV)
PyPI:salt2019.2.5Package registry (OSV)
PyPI:salt2019.2.8Package registry (OSV)
PyPI:salt3000.6Package registry (OSV)
PyPI:salt3000.7Package registry (OSV)
PyPI:salt3001.4Package registry (OSV)
PyPI:salt3001.5Package registry (OSV)
PyPI:salt3002.3Package registry (OSV)
PyPI:salt3002.5Package registry (OSV)
suse:py26-compat-salt2016.11.10-6.8.1 · SUSE:Manager Server Module 4.1Package registry (OSV)
suse:release-notes-susemanager4.0.12.1-3.68.1 · SUSE:Manager Server 4.0Package registry (OSV)
suse:release-notes-susemanager-proxy4.0.12.1-0.16.52.1 · SUSE:Manager Proxy 4.0Package registry (OSV)
suse:salt3000-46.129.1 · SUSE:Manager Client Tools 12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {  // Left empty for the test environment}

Fixed

kotlin
val client = OkHttpClient.Builder()  .certificatePinner(    CertificatePinner.Builder()      .add("api.sirius.example", "sha256/…")      .build()  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records