dbcve.org
Cloud Foundry Uaa BoshApplication · Cloudfoundry

CVE-2016-6636

MEDIUM · 5.3 CVSS v3.0 Published 2016-09-30
Fix available
A fix is available. Upgrade to after 241 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The OAuth authorization implementation 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.1; and Ops Manager 1.7.x before 1.7.13 and 1.8.x before 1.8.1 mishandles redirect_uri subdomains, which allows remote attackers to obtain implicit access tokens via a modified subdomain.

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

The OAuth authorization flow in Pivotal Cloud Foundry and UAA fails to properly validate redirect_uri subdomains, allowing an attacker to register a malicious subdomain that would be accepted as a valid redirect URI. This enables theft of implicit grant access tokens.

MitigationUpgrade PCF components (UAA, Elastic Runtime, Ops Manager) to the patched versions specified in the advisory to fix the redirect_uri subdomain validation logic.

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:<= 12.3
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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 installed UAA version
    Check the UAA version by querying the UAA API endpoint at /uaa/info or reviewing the deployed UAA package manifest. In BOSH deployments, run 'bosh ssh' to the UAA VM and check the release version file.
    Affected if The installed UAA version is <= 12.3, or one of: 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, or 3.0.0
  2. Identify installed Elastic Runtime version
    In the Pivotal Operations Manager UI, navigate to the Elastic Runtime tile and view the version information from the 'Pending Changes' or 'Installation Dashboard' page. Alternatively, query 'cf curl /v2/buildpacks' or check the Pivotal CF product files.
    Affected if The installed Elastic Runtime version is 1.6.0 through 1.6.11 inclusive (any of the listed versions).
  3. Identify installed Ops Manager version
    Access the Pivotal Ops Manager web interface and check the version displayed in the bottom-left corner of the dashboard, or review the Ops Manager VM's installed product version via BOSH.
    Affected if The installed Ops Manager version is 1.7.0 through 1.7.11 inclusive (any of the listed versions).
  4. Check OAuth client configurations for implicit grant
    Query the UAA API to list OAuth clients: 'uaac token owner get' to authenticate, then 'uaac client list' to view registered clients. Examine each client for 'implicit' or 'authorization_code' grant types and note any redirect_uri values containing subdomains.
    Affected if Any OAuth client is configured with implicit grant type AND has a redirect_uri using a subdomain pattern that could be exploited.
  5. Review redirect_uri domain configurations
    Use the UAA API endpoint GET /oauth/clients/{client_id} or the.uaac client get <client_id> command to inspect redirect_uri values. Look for wildcard subdomains or registered domains that may accept arbitrary subdomains as valid redirect targets.
    Affected if Any registered redirect_uri uses a wildcard subdomain pattern or a domain where attackers could register a malicious subdomain.

You are affected if your environment runs any of the specific UAA, Elastic Runtime, or Ops Manager versions listed AND you have OAuth clients using implicit grant with subdomain-based redirect_uri patterns.

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

Upgrade PCF components (UAA, Elastic Runtime, Ops Manager) to the patched versions specified in the advisory to fix the redirect_uri subdomain validation logic.

Fix this in Cloud Foundry Uaa Bosh 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-2016-6636 — 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-6636 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