CVE-2024-22279
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 · uneditedImproper handling of requests in Routing Release > v0.273.0 and <= v0.297.0 allows an unauthenticated attacker to degrade the service availability of the Cloud Foundry deployment if performed at scale.
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 confidenceImproper request handling in Cloud Foundry Routing Release versions greater than v0.273.0 through v0.297.0 allows unauthenticated attackers to send specially crafted HTTP requests that degrade service availability when performed at scale, potentially causing the routing layer to fail or become unresponsive.
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>= 30.9.0, <= 40.13.0>= 0.273.0, <= 0.297.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cloud Foundry Routing Release versionRun 'bosh releases' or check the deployed stemcell manifest for the routing-release. Look for the version number in the release name (e.g., routing-release/0.XXX.0).Affected if The version is between 0.273.0 and 0.297.0 inclusive.
-
Identify Cloud Foundry Cf Deployment versionRun 'cf version' or check the deployment manifest for the cf-deployment version. Look for the release number in the deployment configuration.Affected if The Cf Deployment version is between 30.9.0 and 40.13.0 inclusive.
-
Confirm routing component is deployedQuery 'bosh -d cf-deployment vms' or check the deployment topology for gorouter, routing-api, or tcp-router instances. These are the vulnerable components.Affected if Any routing components (gorouter, routing-api, tcp-router) are running with a vulnerable Routing Release version.
-
Check BOSH deployment manifest for routing-releaseInspect the manifest used for deployment: 'bosh manifest -d cf-deployment > manifest.yml' and search for the routing-release version entry under 'releases:'.Affected if The manifest shows routing-release version within the vulnerable range.
You are affected if your Cloud Foundry environment has either Routing Release between v0.273.0 and v0.297.0 or Cf Deployment between v30.9.0 and v40.13.0 deployed, with routing components actively running.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade the Cloud Foundry Routing Release to a version newer than v0.297.0 to remediate the vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22279 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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