dbcve.org
Cf ReleaseApplication · Cloudfoundry

CVE-2017-4992

CRITICAL · 9.8 CVSS v3.1 Published 2017-06-13
Fix available
A fix is available. Upgrade to after 260 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 v261; UAA release 2.x versions prior to v2.7.4.17, 3.6.x versions prior to v3.6.11, 3.9.x versions prior to v3.9.13, and other versions prior to v4.2.0; and UAA bosh release (uaa-release) 13.x versions prior to v13.15, 24.x versions prior to v24.10, 30.x versions prior to 30.3, and other versions prior to v37. There is privilege escalation (arbitrary password reset) with user invitations.

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

This is a privilege escalation vulnerability in Cloud Foundry's UAA (User Account and Authentication) service that allows arbitrary password reset through the user invitation functionality. An attacker could exploit this to reset any user's password and gain unauthorized access to the platform.

MitigationUpgrade UAA to the patched versions: cf-release v261+, UAA release 2.x v2.7.4.17+/3.6.x v3.6.11+/3.9.x v3.9.13+/4.2.0+, and uaa-release 13.x v13.15+/24.x v24.10+/30.x v30.3+/v37+.

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:<= 260
Cloud Foundry Uaa BoshApplication
Affected:<= 27= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 via bosh deployment
    Run 'bosh deployments' to list deployments, then 'bosh deployment <name>' and look for the uaa release version, or query the UAA endpoint /uaa/info for the version
    Affected if Version is <= 260 for cf-release, <= 27 or between 13.1-13.11 for UAA Bosh, or <= 4.2.0 / 2.7.4.6 for Pivotal UAA
  2. Identify cf-release version
    Run 'bosh deployments' or check the manifest for the cf-release version number
    Affected if Cf-release version is <= 260
  3. Verify user invitation feature is enabled
    Check UAA configuration file (typically in /uaa/uaa.yml or via 'cf curl /uaa/info') for the 'invitationsEnabled' or 'user_invitations' setting set to true
    Affected if User invitation functionality is enabled in UAA config
  4. Check UAA audit logs for suspicious invitation activity
    Review UAA audit logs (via 'bosh logs uaa') for patterns of user invitations to unexpected emails or password resets following invitations
    Affected if Audit logs show unauthorized password resets or suspicious invitation patterns

Environment is affected if UAA version falls within the vulnerable ranges AND user invitation functionality is enabled, allowing an attacker to reset any user password via the invitation endpoint.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 260
Interim mitigation

Upgrade UAA to the patched versions: cf-release v261+, UAA release 2.x v2.7.4.17+/3.6.x v3.6.11+/3.9.x v3.9.13+/4.2.0+, and uaa-release 13.x v13.15+/24.x v24.10+/30.x v30.3+/v37+.

Recommended fix High confidence

cf-release v261+ | UAA 2.7.4.17+ | UAA 3.6.11+ | UAA 3.9.13+ | UAA 4.2.0+ | UAA bosh release 13.15+ | UAA bosh release 24.10+ | UAA bosh release 30.3+ | UAA bosh release 37+

  1. 1. Identify the exact version of Cloud Foundry UAA (User Account and Authentication) currently deployed
  2. 2. Identify the cf-release version if applicable
  3. 3. For UAA release 2.x: Upgrade to version 2.7.4.17 or later
  4. 4. For UAA release 3.6.x: Upgrade to version 3.6.11 or later
  5. 5. For UAA release 3.9.x: Upgrade to version 3.9.13 or later
  6. 6. For UAA release 4.x: Upgrade to version 4.2.0 or later
  7. 7. For UAA bosh release 13.x: Upgrade to version 13.15 or later
  8. 8. For UAA bosh release 24.x: Upgrade to version 24.10 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cf Release Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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