dbcve.org
Capi ReleaseApplication · Cloudfoundry

CVE-2021-22101

HIGH · 7.5 CVSS v3.1 Published 2021-10-27
Fix available
A fix is available. Upgrade to 1.118.0 / 16.24.0 or later.
See remediation →
84/100
Remediation priority · High
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
Cloud Controller versions prior to 1.118.0 are vulnerable to unauthenticated denial of Service(DoS) vulnerability allowing unauthenticated attackers to cause denial of service by using REST HTTP requests with label_selectors on multiple V3 endpoints by generating an enormous SQL query.

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 · high confidence

Cloud Controller versions before 1.118.0 contain an unauthenticated denial of service vulnerability. Attackers can send REST HTTP requests containing label_selectors to multiple V3 API endpoints, which causes the database to generate excessively large SQL queries that consume available resources and cause service failure.

MitigationUpgrade Cloud Controller to version 1.118.0 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.118.0
Cf DeploymentApplication
Affected:< 16.24.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
High

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

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 Cloud Controller version
    Query the Cloud Controller API info endpoint: curl -s https://api.<system-domain>/v3/info or check the capi-release deployment manifest/version file
    Affected if The displayed version is below 1.118.0 for Capi Release or below 16.24.0 for Cf Deployment
  2. Verify V3 API is exposed
    Confirm the Cloud Controller V3 API endpoint is accessible (typically at https://api.<system-domain>/v3). This is the standard REST interface and is enabled by default in Cloud Foundry deployments.
    Affected if The V3 API endpoints are reachable without authentication (unauthenticated access to /v3/* endpoints is the default configuration)
  3. Confirm label selector feature is active
    The label_selectors parameter is a native feature of the V3 API used for filtering resources. Any application or user making GET requests to endpoints like /v3/apps, /v3/spaces, /v3/orgs with label_selector query parameters will trigger the vulnerable code path.
    Affected if The V3 API is active and accepts label_selector query parameters, which is the default behavior for Cloud Controller V3 endpoints

You are affected if your Cloud Controller version is below 1.118.0 (Capi Release) or below 16.24.0 (Cf Deployment) and the V3 API endpoints are accessible, since the vulnerability is triggered by unauthenticated label_selector queries to those endpoints.

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.118.0 / 16.24.0 or later
Fixed in 1.118.016.24.0
Interim mitigation

Upgrade Cloud Controller to version 1.118.0 or later to remediate this vulnerability.

Recommended fix High confidence

Capi Release 1.118.0 or later / Cf Deployment 16.24.0 or later

  1. Identify your current Capi Release or Cf Deployment version using 'cf api' or bosh commands
  2. Review the Cloud Foundry release notes for Capi Release 1.118.0 or Cf Deployment 16.24.0 to understand changes
  3. Test the upgrade in a non-production environment first
  4. Schedule a maintenance window for the upgrade
  5. Upgrade Capi Release to version 1.118.0 or later, or upgrade Cf Deployment to version 16.24.0 or later
  6. Follow standard Cloud Foundry upgrade procedures (bosh deploy)
  7. Verify the upgrade was successful by checking the Cloud Controller version
  8. Test that label_selector queries on V3 endpoints no longer cause excessive SQL query generation
Caveat Standard Cloud Foundry upgrade precautions apply - review release notes for any breaking changes in this release

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

Fix this in Capi Release Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22101 — 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-22101 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