dbcve.org
Cloud Foundry Uaa BoshApplication · Cloudfoundry

CVE-2016-6637

CRITICAL · 9.6 CVSS v3.0 Published 2016-09-30
Fix available
A fix is available. Upgrade to after 241 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Multiple cross-site request forgery (CSRF) vulnerabilities in Pivotal Cloud Foundry (PCF) before 242; UAA 2.x before 2.7.4.7, 3.x before 3.3.0.5, and 3.4.x before 3.4.4; UAA BOSH before 11.5 and 12.x before 12.5; 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 allow remote attackers to hijack the authentication of unspecified victims for requests that approve or deny a scope via a profile or authorize approval page.

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

Multiple CSRF vulnerabilities in Pivotal Cloud Foundry's UAA (User Account and Authentication) component allow remote attackers to hijack victim authentication to approve or deny OAuth scopes via profile or authorization approval pages. The vulnerabilities affect UAA versions 2.x, 3.x, and 3.4.x, along with Elastic Runtime, Ops Manager, and related PCF components.

MitigationUpgrade UAA to version 2.7.4.7+, 3.3.0.5+, or 3.4.4+ and Elastic Runtime/Ops Manager to patched versions per the advisory. Additionally, implement anti-CSRF tokens on state-changing operations in the authorization flow.

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 Uaa BoshApplication
Affected:<= 15.0
Cloud FoundryApplication
Affected:<= 241
Cloud Foundry 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
Cloud Foundry Ops ManagerApplication
Affected:= 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
Cloud Foundry UaaApplication
Affected:= 2.3.0= 2.3.1= 2.4.0= 2.5.1= 2.6.1= 2.7.0.2= 2.7.0.3= 2.7.1= 2.7.2= 2.7.3= 2.7.4.6= 3.0.0

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 component version
    Locate the UAA version by querying the UAA API endpoint /uaa/info or checking the BOSH deployment manifest for the UAA release version
    Affected if UAA version is 2.3.0 through 2.7.4.6, 3.0.0, or any 3.x or 3.4.x version below 3.4.4 (or below 3.3.0.5 for 3.3.x branches)
  2. Identify Cloud Foundry Elastic Runtime version
    Check the Elastic Runtime product version in the Ops Manager tile configuration or via the cf CLI command 'cf curl /v2/info' to retrieve the API version information
    Affected if Elastic Runtime version is 1.6.0 through 1.6.11 inclusive
  3. Identify Ops Manager version
    Check the Ops Manager web UI dashboard for the installed version or query the Ops Manager API endpoint /api/installation
    Affected if Ops Manager version is 1.7.0 through 1.7.11 inclusive
  4. Verify anti-CSRF token presence on OAuth approval endpoints
    Inspect the HTML source of the OAuth authorization approval page (typically at /oauth/authorize) and profile approval page to confirm that a unique, server-generated token is included as a hidden form field or header for all state-changing operations
    Affected if The approval forms lack anti-CSRF tokens (such as state parameter validation or unique per-request tokens) on the scope approval actions

You are affected if your UAA version falls within 2.x, 3.x, or 3.4.x (below 3.4.4), your Elastic Runtime is 1.6.x, or your Ops Manager is 1.7.x, and the OAuth approval pages do not implement anti-CSRF token validation.

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

Upgrade UAA to version 2.7.4.7+, 3.3.0.5+, or 3.4.4+ and Elastic Runtime/Ops Manager to patched versions per the advisory. Additionally, implement anti-CSRF tokens on state-changing operations in the authorization flow.

Recommended fix High confidence

UAA: 2.7.4.7+/3.3.0.5+/3.4.4+; UAA BOSH: 11.5+/12.5+; Elastic Runtime: 1.6.40+/1.7.21+/1.8.2+; Ops Manager: 1.7.13+/1.8.1+; PCF: 242+

  1. Upgrade Cloud Foundry UAA to version 2.7.4.7 or later for 2.x releases, 3.3.0.5 or later for 3.3.x, or 3.4.4 or later for 3.4.x
  2. Upgrade Cloud Foundry UAA BOSH to version 11.5 or later for 11.x, or 12.5 or later for 12.x
  3. Upgrade Cloud Foundry Elastic Runtime to version 1.6.40 or later for 1.6.x, 1.7.21 or later for 1.7.x, or 1.8.2 or later for 1.8.x
  4. Upgrade Cloud Foundry Ops Manager to version 1.7.13 or later for 1.7.x or 1.8.1 or later for 1.8.x
  5. Upgrade overall Pivotal Cloud Foundry (PCF) to version 242 or later
Caveat Review release notes for potential compatibility changes between major versions before upgrading

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

Fix this in Cloud Foundry Uaa Bosh Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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