dbcve.org
Uaa ReleaseApplication · Cloudfoundry

CVE-2019-11279

HIGH · 8.8 CVSS v3.1 Published 2019-09-26
Fix available
A fix is available. Upgrade to 74.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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
CF UAA versions prior to 74.1.0 can request scopes for a client that shouldn't be allowed by submitting an array of requested scopes. A remote malicious user can escalate their own privileges to any scope, allowing them to take control of UAA and the resources it controls.

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

CF UAA versions prior to 74.1.0 contain a scope authorization bypass where a remote attacker can submit an array of requested scopes that exceeds the scopes actually granted to their client, enabling privilege escalation to any scope and full control over UAA and its managed resources.

MitigationUpgrade UAA to version 74.1.0 or later to patch the scope validation vulnerability.

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
Uaa ReleaseApplication
Affected:< 74.1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check UAA version via API
    Query the UAA /info endpoint (e.g., curl https://<uaa-host>/info) and locate the 'version' or 'app' field in the JSON response
    Affected if The returned version string is less than 74.1.0 (e.g., 74.0.0, 73.x.x, etc.)
  2. Check UAA version via BOSH
    Run 'bosh vms' for the UAA deployment and then 'bosh ssh' into the UAA instance to check /var/vcap/packages/uaa_release_version or the UAA manifest at /var/vcap/jobs/uaa/config/uaa.yml
    Affected if The discovered version is prior to 74.1.0
  3. Verify scope validation is in use
    Confirm that UAA is configured to handle OAuth2 client requests with scopes by reviewing the UAA configuration for oauth or scope-related settings
    Affected if UAA is processing scope-based authorization requests and the version is below 74.1.0

The environment is affected if the deployed UAA version is any release prior to 74.1.0, regardless of configuration, since the scope validation flaw is present in the UAA code itself.

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 74.1.0 or later
Fixed in 74.1.0
Interim mitigation

Upgrade UAA to version 74.1.0 or later to patch the scope validation vulnerability.

Fix this in Uaa Release Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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