CVE-2017-8034
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 · uneditedThe Cloud Controller and Router in Cloud Foundry (CAPI-release capi versions prior to v1.32.0, Routing-release versions prior to v0.159.0, CF-release versions prior to v267) do not validate the issuer on JSON Web Tokens (JWTs) from UAA. With certain multi-zone UAA configurations, zone administrators are able to escalate their privileges.
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 and Router in Cloud Foundry fail to validate the issuer claim in JSON Web Tokens (JWTs) received from UAA. In multi-zone UAA configurations, this allows zone administrators to forge tokens and escalate privileges beyond their assigned zone by impersonating other zones' administrators.
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.31.0<= 266<= 0.158.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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/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 if multi-zone UAA is configuredReview UAA configuration for multiple zones: check the UAA manifest or configuration files (typically in cf-release or uaa-release) for multiple zone definitions, or query the UAA API endpoint /uaa/zones to enumerate configured zones.Affected if Multiple zones are defined in UAA configuration (the vulnerability only applies in multi-zone deployments)
-
Check CAPI-release versionRun 'bosh releases' or check the deployed releases via 'cf curl /v2/info' to identify the CAPI-release version number. Compare against the affected version <= 1.31.0.Affected if CAPI-release version is 1.31.0 or lower
-
Check CF-release versionRun 'bosh releases' or use 'cf curl /v2/info' to obtain the cf-release version. Compare against the affected version <= 266.Affected if CF-release version is 266 or lower
-
Check Routing-release versionRun 'bosh releases' to identify the Routing-release version. Compare against the affected version <= 0.158.0.Affected if Routing-release version is 0.158.0 or lower
You are affected if multi-zone UAA is configured AND any of the following are true: CAPI-release <= 1.31.0, CF-release <= 266, or Routing-release <= 0.158.0.
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 Cloud Foundry components to fixed versions: CAPI-release v1.32.0+, Routing-release v0.159.0+, or CF-release v267+. Alternatively, implement issuer validation in the token validation pipeline before the fix is applied.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8034 — 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-8034 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