CVE-2017-14389
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 · uneditedAn issue was discovered in Cloud Foundry Foundation capi-release (all versions prior to 1.45.0), cf-release (all versions prior to v280), and cf-deployment (all versions prior to v1.0.0). The Cloud Controller does not prevent space developers from creating subdomains to an already existing route that belongs to a different user in a different org and space, aka an "Application Subdomain Takeover."
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 Cloud Controller in Cloud Foundry (capi-release, cf-release, cf-deployment) fails to enforce proper authorization checks when creating route subdomains. Space developers can create subdomains pointing to routes owned by users in different organizations and spaces, enabling a subdomain takeover attack where traffic intended for another application's domain can be redirected.
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< 1.45.0< 1.0.0< 280CVSS 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.
-
Identify Cloud Foundry deployment type and versionRun `bosh deployments` to list deployments and their versions, or check the deployment manifest for capi-release, cf-release, or cf-deployment versionAffected if The deployment uses capi-release < 1.45.0, cf-release < 280, or cf-deployment < 1.0.0
-
Query Cloud Controller API versionRun `cf curl /v2/info` to retrieve Cloud Controller API version information and confirm the capi-release versionAffected if The API version corresponds to an affected capi-release version
-
Verify route creation authorizationAs a space developer in Organization A, attempt to create a route with a subdomain that belongs to an application in a different organization using `cf create-route` or the API endpoint /v2/routesAffected if The API allows creating a route subdomain pointing to another organization's domain without authorization errors
-
Check existing route configurations for cross-org subdomainsQuery the Cloud Controller API for routes with hostnames that belong to other organizations: `cf curl /v2/routes?inline-relations-depth=1` and inspect route domain relationshipsAffected if Routes exist where a space developer's route uses a domain from an organization they do not own
The environment is affected if the deployed Cloud Foundry version is below the fixed releases AND the Cloud Controller permits a space developer to create route subdomains pointing to domains owned by different organizations without proper authorization checks.
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 data1.0.01.45.0280
Upgrade to capi-release 1.45.0+, cf-release v280+, or cf-deployment v1.0.0+ which contain proper authorization controls to prevent cross-org/space subdomain route creation.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14389 — 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-2017-14389 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