Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-5399: Cloud Foundry CredHub, versions prior to 2.5.10, connects to a MySQL database without TLS even when configured

47
This month
HIGH 7.4REMOTEWATCHLISTUPGRADEUPGRADE

CVE-2020-5399 is a high-severity flaw (CVSS 7.4) affecting credhub, cloud foundry cf-deployment. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.4 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 55%)
CISA exploited listNo
WeaknessCWE-319
Published2020-02-12
Last modified2026-06-17
Publisher (CNA): Pivotal Software, Inc. · Vendor: cloudfoundry · pivotal software

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

cloudfoundry credhub UPGRADE
Affected: < 2.5.10
Fixed in: 2.5.10
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy credhub || rpm -q credhub || credhub --version
2. UPGRADE to 2.5.10 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade credhub
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade credhub
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
pivotal software cloud foundry cf-deployment UPGRADE
Affected: < 12.29.0
Fixed in: 12.29.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy cloud-foundry-cf-deployment || rpm -q cloud-foundry-cf-deployment || cloud-foundry-cf-deployment --version
2. UPGRADE to 12.29.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade cloud-foundry-cf-deployment
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade cloud-foundry-cf-deployment
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
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-5399?

credhub: upgrade to 2.5.10; cloud foundry cf-deployment: upgrade to 12.29.0. Exact commands for each OS are on this page.

Is CVE-2020-5399 being exploited?

CVE-2020-5399 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-5399 affect?

CVE-2020-5399 affects credhub, cloud foundry cf-deployment. Severity is high (CVSS 7.4). 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 connecti

How urgent is CVE-2020-5399?

Priority 47/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

MySQL vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.