dbcve.org
Cf ReleaseApplication · Cloudfoundry

CVE-2017-4991

HIGH · 7.2 CVSS v3.1 Published 2017-06-13
Fix available
A fix is available. Upgrade to after 259 or later.
See remediation →
78/100
Remediation priority · High
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
An issue was discovered in Cloud Foundry Foundation cf-release versions prior to v260; UAA release 2.x versions prior to v2.7.4.16, 3.6.x versions prior to v3.6.10, 3.9.x versions prior to v3.9.12, and other versions prior to v3.17.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.14, 24.x versions prior to v24.9, 30.x versions prior to 30.2, and other versions prior to v36. Privileged users in one zone are allowed to perform a password reset for users in a different zone.

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

A zone isolation bypass vulnerability in Cloud Foundry's UAA (User Account and Authentication) server allows privileged users (zone admins) in one zone to perform password resets for users in a different zone, violating multi-tenant isolation boundaries.

MitigationUpgrade UAA to patched versions: cf-release to v260+, UAA release to v3.17.0+/v3.9.12+/v3.6.10+/v2.7.4.16+, or uaa-release to v36+/v30.2+/v24.9+/v13.14+. Review zone admin permissions and monitor for unauthorized cross-zone password reset activity.

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:<= 259
Cloud Foundry Uaa BoshApplication
Affected:<= 35= 13.1= 13.2= 13.3= 13.4= 13.5= 13.6= 13.7= 13.8= 13.9= 13.10= 13.11
Cloud Foundry UaaApplication
Affected:<= 4.2.0= 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

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

CVSS:3.1/AV:N/AC:L/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 UAA version
    Locate the UAA server version by querying the /info endpoint of the UAA API (e.g., curl https://uaa.your-domain/info) or check the BOSH deployment manifest for the uaabosh or uaa-release job version
    Affected if The installed version matches any of the affected ranges: Cf Release <= 259, UAA Bosh <= 35 or versions 13.1-13.11, Pivotal UAA <= 4.2.0 or versions 2.2.5.4, 2.7.1-2.7.4.6
  2. Confirm multi-tenant zone configuration
    Query the UAA zones endpoint (e.g., /uaa/zones) using an admin token to list all configured zones. Check if multiple zones exist beyond the default zone
    Affected if Multiple zones are configured and the UAA version is in the affected list
  3. Identify zone admin users
    List users granted zone-admin scope in each non-default zone by querying /uaa/zones/{zone-id}/users or reviewing UAA group memberships for the zoneadmin group
    Affected if Zone admin users exist in any non-default zone and the UAA version is vulnerable
  4. Verify cross-zone password reset behavior
    Using a zone admin token from one zone, attempt a password reset request for a user in a different zone (POST /uaa/zones/{target-zone}/users/{user-id}/password) and observe if it succeeds when it should be denied
    Affected if The password reset succeeds for a user in a different zone, indicating the isolation bypass is present
  5. Review audit logs for cross-zone password resets
    Search UAA audit logs (typically in theuaa.log or via the logging endpoint) for password_reset events where the zone context differs from the target user's zone
    Affected if Audit logs show password reset events where the requesting zone admin belongs to a different zone than the user whose password was reset

Your environment is affected if the UAA version falls within the vulnerable ranges AND multiple zones with zone admins are configured, allowing cross-zone password resets to succeed.

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

Upgrade UAA to patched versions: cf-release to v260+, UAA release to v3.17.0+/v3.9.12+/v3.6.10+/v2.7.4.16+, or uaa-release to v36+/v30.2+/v24.9+/v13.14+. Review zone admin permissions and monitor for unauthorized cross-zone password reset activity.

Fix this in Cf Release 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-4991 — 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-4991 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