CVE-2019-11278
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 · uneditedCF UAA versions prior to 74.1.0, allow external input to be directly queried against. A remote malicious user with 'client.write' and 'groups.update' can craft a SCIM query, which leaks information that allows an escalation of privileges, ultimately allowing the malicious user to gain control of UAA scopes they should not have.
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 confidenceThis is a SCIM (System for Cross-domain Identity Management) query injection vulnerability in Cloud Foundry UAA (User Account and Authentication) that allows authenticated attackers with 'client.write' and 'groups.update' permissions to craft malicious SCIM queries that leak sensitive information, enabling privilege escalation to gain control of UAA scopes they should not have access to.
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< 74.1.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.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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed UAA versionQuery the UAA /info endpoint (e.g., curl https://uaa.example.com/info) or check the UAA release manifest file for the version fieldAffected if The reported version is less than 74.1.0
-
Confirm SCIM endpoint accessibilityVerify the /Users SCIM endpoint is accessible (e.g., GET https://uaa.example.com/Users?startIndex=1)Affected if The SCIM endpoint responds to authenticated requests
-
Identify clients or users with client.write permissionQuery the UAA for clients or users granted the 'clients.write' authority. This can be done via the UAA API: GET /oauth/clients or by reviewing client configuration filesAffected if Any client or user account possesses the 'client.write' permission
-
Identify clients or users with groups.update permissionQuery the UAA for users or clients granted the 'groups.update' authority. Use the UAA API: GET /Users or check group membership configurationsAffected if Any client or user account possesses the 'groups.update' permission
-
Check for combined vulnerable permissionsCross-reference results from steps 3 and 4 to identify if any single principal (user or client) has BOTH 'client.write' AND 'groups.update' permissions simultaneouslyAffected if A single authenticated principal has both permissions granted
Your environment is affected if UAA version is below 74.1.0 AND at least one authenticated principal holds both 'client.write' and 'groups.update' permissions in your UAA deployment.
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 data74.1.0
Upgrade UAA to version 74.1.0 or later. Until patched, strictly limit and audit users granted 'client.write' and 'groups.update' permissions as these are required for exploitation.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-11278 — 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-2019-11278 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