dbcve.org
Cf ReleaseApplication · Cloudfoundry

CVE-2016-0732

HIGH · 8.8 CVSS v3.1 Published 2017-09-07
Fix available
A fix is available. Upgrade to after 229 or later.
See remediation →
94/100
Remediation priority · Urgent
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
The identity zones feature in Pivotal Cloud Foundry 208 through 229; UAA 2.0.0 through 2.7.3 and 3.0.0; UAA-Release 2 through 4, when configured with multiple identity zones; and Elastic Runtime 1.6.0 through 1.6.13 allows remote authenticated users with privileges in one zone to gain privileges and perform operations on a different zone via unspecified vectors.

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

Cross-zone privilege escalation vulnerability in the UAA (User Account and Authentication) component of Pivotal Cloud Foundry. When multiple identity zones are configured, the identity zones feature allows authenticated users with privileges in one zone to improperly gain privileges and perform operations in a different zone, bypassing zone isolation boundaries.

MitigationUpdate UAA to version 2.7.4 or 3.0.1 or later, and Cloud Foundry to patched releases. Review and enforce proper zone isolation configuration in multi-zone deployments.

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
Cf ReleaseApplication
Affected:>= 208, <= 229
User Account And AuthenticationApplication
Affected:= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.1.0= 2.2.0= 2.2.1= 2.2.2= 2.2.3= 2.2.4= 2.2.4.1= 2.2.5
Uaa ReleaseApplication
Affected:= 2= 3= 4
Elastic RuntimeApplication
Affected:= 1.6.0= 1.6.1= 1.6.2= 1.6.3= 1.6.4= 1.6.5= 1.6.6= 1.6.7= 1.6.8= 1.6.9= 1.6.10= 1.6.11

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine UAA component version
    Query the UAA /info endpoint or check the deployment manifest: curl -k https://uaa.your-domain.com/info or review the cf-release/uaa-release manifest files in your deployment repository
    Affected if The UAA version is 2.0.0 through 2.2.5, or Uaa Release versions 2, 3, or 4, or if Cloud Foundry Cf Release is between 208 and 229 inclusive, or Pivotal Elastic Runtime is 1.6.0 through 1.6.11
  2. Verify if multiple identity zones are configured
    Query the UAA zones endpoint using an admin token: curl -k -H 'Authorization: bearer TOKEN' https://uaa.your-domain.com/uaa/zones or review UAA configuration YAML files for multiple zone definitions under the zones: section
    Affected if More than one identity zone is defined in the UAA configuration, which enables the vulnerable cross-zone access path
  3. Check for cross-zone user permissions
    Review user/group mappings in each zone by querying the UAA users endpoint for each zone (uaa.zone1.domain.com/uaa/users and uaa.zone2.domain.com/uaa/users) or examine the UAA database scim_tables for users with elevated privileges across zones
    Affected if A user account exists in one zone but has been granted scopes, roles, or permissions that should be isolated to another zone, indicating zone isolation has been bypassed
  4. Confirm identity zone isolation configuration
    Inspect the UAA configuration file (typically uaa.yml or manifest.yml) for the property zoneHierarchy or check that each zone's issuer URI is properly segmented and that internal_api or token endpoint is not shared across zones
    Affected if Zones share the same internal API endpoint, issuer URI, or have zoneHierarchy set in a way that allows tokens from one zone to be valid in another zone

You are affected if your UAA version falls within 2.0.0-2.2.5 (or Uaa Release 2-4, Cf Release 208-229, or Elastic Runtime 1.6.0-1.6.11) AND you have multiple identity zones configured with improper isolation between them.

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 229
Interim mitigation

Update UAA to version 2.7.4 or 3.0.1 or later, and Cloud Foundry to patched releases. Review and enforce proper zone isolation configuration in multi-zone deployments.

Fix this in Cf Release Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0732 — 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-2016-0732 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