Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-5417: Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain

46
This month
HIGH 8.8UPGRADEUPGRADE

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

Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain is also the system domain (which is true in the default CF Deployment manifest), were vulnerable to developers maliciously or accidentally claiming certain sensitive routes, potentially resulting in the developer's app handling some requests that were expected to go to certain system components.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance1.0% (top 38%)
CISA exploited listNo
WeaknessCWE-732
Published2020-08-21
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.97.0
Fixed in: 1.97.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.97.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: < 13.12.0
Fixed in: 13.12.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 13.12.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-5417?

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

Is CVE-2020-5417 being exploited?

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

CVE-2020-5417 affects capi-release, cf-deployment. Severity is high (CVSS 8.8). Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain is also the system domain (which is true in the default CF Deployment manifest), were vulnerable to developers maliciously or acc

How urgent is CVE-2020-5417?

Priority 46/100. High severity

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.