CVE-2020-5426 json
Scheduler for TAS can transmit privileged UAA token in plaintext
published 2020-11-11 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-26594
- cvss
- 8.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
Scheduler for TAS prior to version 1.4.0 was permitting plaintext transmission of UAA client token by sending it over a non-TLS connection. This also depended on the configuration of the MySQL server which is used to cache a UAA client token used by the service. If intercepted the token can give an attacker admin level access in the cloud controller.
Patch / fix
- VMware Tanzu Pivotal Scheduler 1.4.0
Exploit prediction
0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.6 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- VMware Tanzu Pivotal Scheduler
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
tanzu.vmware.com
/security/cve-2020-5426
third-party-advisory
Sources
- CVE List CVE-2020-5426
- NVD CVE-2020-5426
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.