dbcve.org
Capi ReleaseApplication · Cloudfoundry

CVE-2021-22100

MEDIUM · 5.3 CVSS v3.1 Published 2022-03-25
Fix available
A fix is available. Upgrade to 1.122.0 / 17.1.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A denial-of-service vulnerability in Cloud Foundry CAPI (Cloud Controller API) versions prior to 1.122 allows a developer to push a service broker that causes Cloud Controller instances to timeout and fail, rendering the platform unable to process app pushes or manage existing applications.

MitigationUpgrade Cloud Foundry CAPI to version 1.122 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Capi ReleaseApplication
Affected:< 1.122.0
Cf DeploymentApplication
Affected:< 17.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check CAPI release version
    Use BOSH to query the deployed CAPI release version: `bosh -d DEPLOYMENT_NAME releases | grep capi` or inspect the deployment manifest for the capi-release version
    Affected if The CAPI release version is earlier than 1.122.0
  2. Check cf-deployment version
    Query the cf-deployment version from your deployment manifest or BOSH deployments: `bosh -d cf deployments` and check the stemcell and release versions
    Affected if The cf-deployment version is earlier than 17.1.0
  3. Verify Cloud Controller API is exposed
    Run `cf api` to confirm the Cloud Controller API endpoint is configured and accessible
    Affected if The CF API endpoint is active and processing requests from the affected version range
  4. Confirm service broker functionality is enabled
    Check if any service brokers are registered: `cf service-brokers` or `cf curl /v2/service_brokers`
    Affected if Any service broker is registered in the environment (the vulnerability is triggered when a malicious broker is pushed)

The environment is affected if the CAPI release is below 1.122.0 or cf-deployment is below 17.1.0, and the Cloud Controller API with service broker functionality is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.122.0 / 17.1.0 or later
Fixed in 1.122.017.1.0
Interim mitigation

Upgrade Cloud Foundry CAPI to version 1.122 or later to remediate this vulnerability.

Recommended fix High confidence

CAPI Release >= 1.122.0 or CF Deployment >= 17.1.0

  1. Back up current Cloud Foundry deployment configuration and state
  2. Upgrade CAPI Release to version 1.122.0 or later (or upgrade CF Deployment to 17.1.0 or later)
  3. Deploy the upgraded CAPI release using your Cloud Foundry deployment method (e.g., BOSH deploy or cf-deployment upgrade)
  4. Verify that all Cloud Controller (CC) instances are running and responsive
  5. Confirm the service broker API endpoints are functioning correctly without timeouts
  6. Test app push and app management operations to ensure the DoS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Capi Release Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22100 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data