CVE-2016-6651
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 UAA /oauth/token endpoint in Pivotal Cloud Foundry (PCF) before 243; UAA 2.x before 2.7.4.8, 3.x before 3.3.0.6, and 3.4.x before 3.4.5; UAA BOSH before 11.7 and 12.x before 12.6; Elastic Runtime before 1.6.40, 1.7.x before 1.7.21, and 1.8.x before 1.8.2; and Ops Manager 1.7.x before 1.7.13 and 1.8.x before 1.8.1 allows remote authenticated users to gain privileges by leveraging possession of a token.
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 · moderate confidencePrivilege escalation vulnerability in the UAA /oauth/token endpoint where an authenticated user with a valid token can leverage it to gain elevated privileges beyond what their token should originally permit.
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<= 16.0<= 242.0= 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= 1.7.0= 1.7.1= 1.7.2= 1.7.3= 1.7.4= 1.7.5= 1.7.6= 1.7.7= 1.7.8= 1.7.9= 1.7.10= 1.7.11<= 3.7.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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify UAA versionQuery the UAA health endpoint or check the deployed UAA package version. On Cloud Foundry, run 'cf curl /uaa/info' or check the manifest.yml for the UAA release version.Affected if The installed UAA version is 3.7.0 or earlier, or UAA BOSH release 16.0 or earlier
-
Confirm Elastic Runtime versionRun 'cf curl /v2/info' or check the Elastic Runtime tile version in Ops Manager. The cf CLI command 'cf version' shows the API version, not the runtime version; check Ops Manager for the exact Elastic Runtime version.Affected if Elastic Runtime version is 1.6.0 through 1.6.11 (any listed version in that range)
-
Confirm Ops Manager versionCheck the Ops Manager web UI dashboard or run 'omcurl' against the Ops Manager API to retrieve the installed version.Affected if Ops Manager version is 1.7.0 through 1.7.11 (any listed version in that range)
-
Check if OAuth token endpoint is exposedReview UAA configuration in manifest.yml or the OAuth client settings. Verify the /oauth/token endpoint is accessible by attempting a token request with a valid but low-privilege user token.Affected if The /oauth/token endpoint accepts requests and the UAA is in the affected version range
You are affected if your deployed UAA version is 3.7.0 or earlier, UAA BOSH is 16.0 or earlier, Elastic Runtime is any 1.6.x version up to 1.6.11, or Ops Manager is any 1.7.x version up to 1.7.11, and the OAuth token endpoint is enabled.
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 to patched versions: UAA 2.7.4.8+, 3.3.0.6+, 3.4.5+; Elastic Runtime 1.6.40+, 1.7.21+, 1.8.2+; Ops Manager 1.7.13+, 1.8.1+; UAA BOSH 11.7+ or 12.6+.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6651 — 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-2016-6651 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