dbcve.org
Cloud Foundry UaaApplication · Pivotal Software

CVE-2017-8032

MEDIUM · 6.6 CVSS v3.0 Published 2017-07-10
Fix available
A fix is available. Upgrade to after 263 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
In Cloud Foundry cf-release versions prior to v264; UAA release all versions of UAA v2.x.x, 3.6.x versions prior to v3.6.13, 3.9.x versions prior to v3.9.15, 3.20.x versions prior to v3.20.0, and other versions prior to v4.4.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.17, 24.x versions prior to v24.12. 30.x versions prior to 30.5, and other versions prior to v41, zone administrators are allowed to escalate their privileges when mapping permissions for an external provider.

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 confidence

Zone administrators in Cloud Foundry UAA can escalate privileges by mapping permissions for external identity providers, allowing unauthorized access beyond their intended authorization level.

MitigationUpgrade UAA to patched versions (v3.6.13+, v3.9.15+, v3.20.0+, v4.4.0+, v13.17+, v24.12+, v30.5+, v41+) and verify zone admin permissions are properly scoped.

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
Cloud Foundry UaaApplication
Affected:= 2.2.5.4= 2.7.1= 2.7.2= 2.7.3= 2.7.4= 2.7.4.1= 2.7.4.2= 2.7.4.3= 2.7.4.4= 2.7.4.5= 2.7.4.6= 2.7.4.7
Cloud Foundry Uaa BoshApplication
Affected:<= 40= 13.1= 13.2= 13.3= 13.4= 13.5= 13.6= 13.7= 13.8= 13.9= 13.10= 13.11
Cloud Foundry CfApplication
Affected:<= 263

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed UAA version
    Run 'uaac target' and then 'uaac version' or check the UAA package/version file in the deployment. Alternatively, query the UAA info endpoint: 'uaac curl /info' and look for the 'version' field in the response.
    Affected if The reported version matches any of the affected versions: 2.2.5.4, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.7.4.1 through 2.7.4.7, or UAA Bosh versions 40 or lower, or versions 13.1 through 13.11, or Cloud Foundry Cf version 263 or lower.
  2. Verify zone administrator accounts exist
    Use 'uaac clients --zone' or query the UAA client registry to list users with 'zone.admin' scope. Check if any user accounts hold the zone administrator role in non-default zones.
    Affected if Zone administrator accounts are present in the UAA system, particularly in zones other than the default zone.
  3. Check for external identity provider configuration
    Review the UAA configuration YAML files or use 'uaac identity-zone list' to enumerate configured identity zones. Then inspect each zone's SAML or OAuth identity provider settings using the UAA admin API endpoint '/identity-zones/{zone-id}/saml/config' or '/identity-zones/{zone-id}/oauth/config'.
    Affected if External identity providers (SAML, OAuth, LDAP) are configured within any UAA zone, especially in non-default zones.
  4. Audit zone admin permission mappings
    Query the UAA to list all permission mappings for zone administrators using the admin API: 'uaac curl -H "Authorization: Bearer $TOKEN" /identity-zones/{zone-id}/permissions' or review the UAA database permission tables if direct database access is available.
    Affected if Zone administrators have permissions that allow them to modify or create identity provider attribute mappings.

The environment is affected if the installed UAA version matches any of the affected versions AND zone administrators with external identity provider configuration access exist in the deployment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 263
Interim mitigation

Upgrade UAA to patched versions (v3.6.13+, v3.9.15+, v3.20.0+, v4.4.0+, v13.17+, v24.12+, v30.5+, v41+) and verify zone admin permissions are properly scoped.

Fix this in Cloud Foundry Uaa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8032 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8032 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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