Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-5423: CAPI (Cloud Controller) versions prior to 1.101.0 are vulnerable to a denial-of-service attack in which an una

48
This month
HIGH 7.5REMOTEUPGRADEUPGRADE

CVE-2020-5423 is a high-severity flaw (CVSS 7.5) affecting capi-release, cf-deployment. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

CAPI (Cloud Controller) versions prior to 1.101.0 are vulnerable to a denial-of-service attack in which an unauthenticated malicious attacker can send specially-crafted YAML files to certain endpoints, causing the YAML parser to consume excessive CPU and RAM.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.1% (top 33%)
CISA exploited listNo
WeaknessCWE-400
Published2020-12-02
Last modified2026-06-17
Publisher (CNA): Pivotal Software, Inc. · Vendor: cloudfoundry

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

capi-release: upgrade to 1.101.0; cf-deployment: upgrade to 15.0.0. Exact commands for each OS are on this page.

Is CVE-2020-5423 being exploited?

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

CVE-2020-5423 affects capi-release, cf-deployment. Severity is high (CVSS 7.5). CAPI (Cloud Controller) versions prior to 1.101.0 are vulnerable to a denial-of-service attack in which an unauthenticated malicious attacker can send specially-crafted YAML files to certain endpoints, causing the YAML parser to consume exc

How urgent is CVE-2020-5423?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

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.