CVE-2023-34061
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 · uneditedCloud Foundry routing release versions from v0.163.0 to v0.283.0 are vulnerable to a DOS attack. An unauthenticated attacker can use this vulnerability to force route pruning and therefore degrade the service availability of the Cloud Foundry deployment.
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 confidenceCloud Foundry routing release versions v0.163.0 through v0.283.0 contain a vulnerability allowing unauthenticated attackers to trigger forced route pruning, resulting in denial of service through degraded service availability.
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>= 0.28.0, <= 33.5.0>= 0.163.0, <= 0.283.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.
-
Check the installed Routing Release versionRun 'bosh -e <environment> releases' or check the deployment manifest for the routing-release version under the releases section. Look for the version number in the format v0.xxxxAffected if The routing release version is between v0.163.0 and v0.283.0 inclusive
-
Verify the PCF Deployment versionRun 'bosh -e <environment> deployments' or check the ops manager UI for the Pivotal Cloud Foundry deployment version. Check the product deployment manifestAffected if The deployment version is between 0.28.0 and 33.5.0 inclusive
-
Confirm the routing API is externally accessibleCheck the routing manifest or config for 'router_status' or 'routing_api' endpoint exposure. Look for routes in the manifest under properties.router.status or routing_api section that bind to an external IPAffected if The routing API status endpoint is reachable from untrusted networks without authentication
-
Inspect route pruning configurationCheck the routing-release manifest for pruning-related settings. Look for 'pruning' or 'garbage_collection' settings in the router or route_emitter job configurationsAffected if Route pruning is enabled and can be triggered by unauthenticated requests
A user is affected if their Cloud Foundry deployment uses routing release v0.163.0 through v0.283.0 (or PCF deployment 0.28.0 through 33.5.0) with an exposed routing API that accepts unauthenticated requests
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.
dbcve · scopedUpgrade the Cloud Foundry routing release to a version newer than v0.283.0 to remediate this vulnerability.
Cloud Foundry Routing Release >= 0.284.0
- Upgrade Cloud Foundry Routing Release to version 0.284.0 or later
- After upgrading, verify that route pruning functions normally and service availability is restored
- Monitor the deployment for any unexpected behavior following the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34061 — 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-2023-34061 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