CVE-2020-5399 json
CredHub does not properly enable TLS for MySQL database connections
published 2020-02-12 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-26578
- cvss
- 7.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
Cloud Foundry CredHub, versions prior to 2.5.10, connects to a MySQL database without TLS even when configured to use TLS. A malicious user with access to the network between CredHub and its MySQL database may eavesdrop on database connections and thereby gain unauthorized access to CredHub and other components.
Patch / fix
- Cloud Foundry CredHub 2.5.10
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.6 | CVSS:3.0/AV:A/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Affected products
- Cloud Foundry CredHub
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
cloudfoundry.org
/blog/cve-2020-5399
vendor-advisory
Sources
- CVE List CVE-2020-5399
- NVD CVE-2020-5399
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.