CVE-2020-5426
Scheduler for TAS can transmit privileged UAA token in plaintext
Reported by pivotal · Published November 11, 2020
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Pivotal Scheduler | VMware Tanzu | 1.4.0 |
| pivotal_scheduler | vmware | 1.4.0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| VMware Tanzu | Pivotal Scheduler | All |
| VMware Tanzu | Pivotal Scheduler | * |
Timeline
- Nov 11, 2020 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Sep 17, 2024 CVE Updated
- Apr 4, 2026 Security Advisory
- Aug 30, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2020-5426
vulnetix vdb fixes CVE-2020-5426
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-5426/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart