CVE-2019-3789
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, all versions prior to 0.188.0, contains a vulnerability that can hijack the traffic to route services hosted outside the platform. A user with space developer permissions can create a private domain that shadows the external domain of the route service, and map that route to an app. When the gorouter receives traffic destined for the external route service, this traffic will instead be directed to the internal app using the shadow route.
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 confidenceA routing shadowing vulnerability in Cloud Foundry's gorouter allows a space developer to create a private domain that shadows external route service domains. When the gorouter receives traffic for the external service, it redirects to the attacker's internal application instead, enabling traffic hijacking.
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.188.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 Cloud Foundry Routing Release versionQuery the BOSH deployment for the gorouter release version using `bosh deployments` and `bosh vms -d cf-routing`, or check the stemcell manifest for the routing-release versionAffected if The installed routing release version is below 0.188.0
-
Identify space developer role assignmentsUse `cf org-users <org_name>` and `cf space-users <org> <space>` to list users with Space Developer role, or query the UAA API for role assignmentsAffected if Any user possesses Space Developer role in any space within an org that contains the affected gorouter
-
Enumerate private domains in the foundationRun `cf domains` to list all domains, noting which are marked as 'private' or internal. Cross-reference with known external route service domainsAffected if Private domains exist that share names with external route service domains (e.g., matching the hostname of SaaS or external service routes)
-
Review gorouter route table for shadowed routesInspect the gorouter's routing table via its debug endpoint (if exposed) or check route configuration in the Cloud Foundry database (ccdb.routes table) for route conflictsAffected if Routes exist where an internal private domain matches an external service domain, causing the gorouter to route to an internal app instead of the external service
You are affected if the Routing Release is below 0.188.0 AND any Space Developer can create private domains that shadow external route service domains.
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.188.0
Upgrade Cloud Foundry Routing Release to version 0.188.0 or later, and audit/revoke unnecessary space developer permissions to prevent domain shadowing.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3789 — 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-3789 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