CVE-2020-5425: Single Sign-On for Vmware Tanzu all versions prior to 1.11.3 ,1.12.x versions prior to 1.12.4 and 1.13.x prior

This month

HIGH 7.9UPGRADE

CVE-2020-5425 is a high-severity flaw (CVSS 7.9) affecting single sign-on for tanzu. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Single Sign-On for Vmware Tanzu all versions prior to 1.11.3 ,1.12.x versions prior to 1.12.4 and 1.13.x prior to 1.13.1 are vulnerable to user impersonation attack.If two users are logged in to the SSO operator dashboard at the same time, with the same username, from two different identity providers, one can acquire the token of the other and thus operate with their permissions. Note: Foundation may be vulnerable only if: 1) The system zone is s

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.9 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-287
Published	2020-10-31
Last modified	2026-06-17

Publisher (CNA): Pivotal Software, Inc. · Vendor: vmware

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-10-31 22:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

vmware single sign-on for tanzu UPGRADE

Affected: < 1.11.3 · >= 1.12.0 and < 1.12.4 · >= 1.13.0 and < 1.13.1

Fixed in: 1.11.3, 1.12.4, 1.13.1

Safe to downgrade to: a release before 1.12.0

1. Check installed version

apt-cache policy single-sign-on-for-tanzu || rpm -q single-sign-on-for-tanzu || single-sign-on-for-tanzu --version

2. UPGRADE to 1.11.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade single-sign-on-for-tanzu

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade single-sign-on-for-tanzu

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.12.0 (Debian / Ubuntu)

apt-cache madison single-sign-on-for-tanzu sudo apt install single-sign-on-for-tanzu=<VERSION_BEFORE_1.12.0> sudo apt-mark hold single-sign-on-for-tanzu

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list single-sign-on-for-tanzu sudo dnf downgrade single-sign-on-for-tanzu-<VERSION_BEFORE_1.12.0> sudo dnf versionlock add single-sign-on-for-tanzu

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5425?

single sign-on for tanzu: upgrade to 1.11.3, 1.12.4, 1.13.1. Exact commands for each OS are on this page.

Is CVE-2020-5425 being exploited?

CVE-2020-5425 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5425 affect?

CVE-2020-5425 affects single sign-on for tanzu. Severity is high (CVSS 7.9). Single Sign-On for Vmware Tanzu all versions prior to 1.11.3 ,1.12.x versions prior to 1.12.4 and 1.13.x prior to 1.13.1 are vulnerable to user impersonation attack.If two users are logged in to the SSO operator dashboard at the same time,

How urgent is CVE-2020-5425?

Priority 41/100. High severity

Software pages

VMware vulnerabilities

References

← Back to latest CVEs