CVE-2019-11289
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, all versions before 0.193.0, does not properly validate nonce input. A remote unauthenticated malicious user could forge an HTTP route service request using an invalid nonce that will cause the Gorouter to crash.
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 confidenceThe Gorouter component in Cloud Foundry fails to properly validate nonce input in HTTP route service requests. An unauthenticated remote attacker can send specially crafted requests with invalid nonces that cause the Gorouter to crash, resulting in denial of service.
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< 12.8.0< 0.193.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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Cloud Foundry Routing Release versionRun 'bosh -d deployment-name vms' and inspect the gorouter job release version, or query the Routing Release using 'bosh releases' to find the installed version numberAffected if The installed Routing Release version is below 0.193.0
-
Check Cf Deployment versionRun 'cf target' and review the API version, or check the cf-deployment manifest version using 'bosh -d cf-deployment manifest'Affected if The Cf Deployment version is below 12.8.0
-
Verify if route services are enabledRun 'cf routes' to list routes, then check if any route service is bound using 'cf route-services' or inspect the Gorouter configuration at /var/vcap/jobs/gorouter/config/gorouter.yml for route_service configurationAffected if Route services are configured and in use in the environment
-
Review Gorouter logs for crash eventsInspect gorouter logs using 'bosh logs gorouter --recent' and search for terms like 'nonce', 'panic', or 'crash' related to route service requestsAffected if Recent gorouter crashes are logged with route service nonce validation errors
A user is affected if their Cloud Foundry environment is running Routing Release below 0.193.0 or Cf Deployment below 12.8.0 AND has route services enabled or in use.
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 data0.193.012.8.0
Upgrade Cloud Foundry Routing to version 0.193.0 or later to implement proper nonce validation and prevent denial of service attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.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 $4,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11289 — 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-2019-11289 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