CVE-2019-11274
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 · uneditedCloud Foundry UAA, versions prior to 74.0.0, is vulnerable to an XSS attack. A remote unauthenticated malicious attacker could craft a URL that contains a SCIM filter that contains malicious JavaScript, which older browsers may execute.
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 confidenceCross-site scripting (XSS) vulnerability in Cloud Foundry UAA (User Account and Authentication) server versions prior to 74.0.0. A remote unauthenticated attacker can inject malicious JavaScript into a SCIM filter parameter within a crafted URL, which older browsers may execute.
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.0.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed UAA versionCheck the UAA version by querying the /info endpoint (e.g., curl https://<uaa-host>/info) or by inspecting the release manifest/releasedocker image version. The version is typically exposed in the 'version' or 'app' field of the JSON response.Affected if The version displayed is less than 74.0.0 (e.g., 73.x.x, 72.x.x, etc.)
-
Verify SCIM endpoint is enabledCheck the UAA configuration files (typically uaa.yml or manifest.yml) for the 'scim' service configuration. Alternatively, attempt to access the SCIM endpoint at /uaa/Users with a filter parameter.Affected if SCIM is enabled and the endpoint is accessible without authentication or with low-privilege access
-
Confirm UAA is web-accessibleVerify that the UAA server is reachable over HTTP/HTTPS from browsers. Test by accessing the login page or the /uaa/ endpoint.Affected if The UAA web interface is exposed to browsers that could execute the injected JavaScript from a crafted URL
-
Review SCIM filter parameter handlingInspect any available UAA logs for suspicious requests containing JavaScript in SCIM filter parameters (e.g., ?filter=...<script>...). Check if URL encoding is properly applied.Affected if Logs show unencoded or improperly sanitized filter parameters in SCIM queries
You are affected if your UAA version is below 74.0.0 AND the SCIM endpoint is enabled and web-accessible, allowing a crafted URL with malicious JavaScript in a SCIM filter parameter to be executed by older browsers.
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.0.0
Upgrade UAA to version 74.0.0 or later to address the XSS vulnerability in the SCIM filter.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11274 — 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-11274 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