Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2021-22100: In cloud foundry CAPI versions prior to 1.122, a denial-of-service attack in which a developer can push a serv

39
Routine
MEDIUM 5.3REMOTEUPGRADEUPGRADE

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

In cloud foundry CAPI versions prior to 1.122, a denial-of-service attack in which a developer can push a service broker that (accidentally or maliciously) causes CC instances to timeout and fail is possible. An attacker can leverage this vulnerability to cause an inability for anyone to push or manage apps.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.9% (top 40%)
CISA exploited listNo
WeaknessCWE-400
Published2022-03-25
Last modified2026-06-17
Publisher (CNA): VMware · 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.122.0
Fixed in: 1.122.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.122.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: < 17.1.0
Fixed in: 17.1.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 17.1.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-2021-22100?

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

Is CVE-2021-22100 being exploited?

CVE-2021-22100 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-2021-22100 affect?

CVE-2021-22100 affects capi-release, cf-deployment. Severity is medium (CVSS 5.3). In cloud foundry CAPI versions prior to 1.122, a denial-of-service attack in which a developer can push a service broker that (accidentally or maliciously) causes CC instances to timeout and fail is possible. An attacker can leverage this v

How urgent is CVE-2021-22100?

Priority 39/100. 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.