CVE-2019-11290
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 Release, versions prior to v74.8.0, logs all query parameters to tomcat’s access file. If the query parameters are used to provide authentication, ie. credentials, then they will be logged as well.
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 confidenceCloud Foundry UAA Release versions prior to v74.8.0 write all HTTP query parameters to Tomcat's access log files. When query parameters contain authentication credentials (such as in OAuth or login requests), these sensitive values are persisted in plain text logs, creating a credential disclosure 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< 12.10.0< 74.8.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify UAA versionCheck the installed version of Cloud Foundry User Account and Authentication (UAA) by running 'uaac version' or inspecting the UAA release manifest file. Compare this version number against the affected range (versions prior to 74.8.0).Affected if The installed UAA version is lower than 74.8.0
-
Identify Cf Deployment versionCheck the Cloud Foundry deployment version by running 'cf version' or inspecting the deployment manifest. Compare this version number against the affected range (versions prior to 12.10.0).Affected if The installed Cf Deployment version is lower than 12.10.0
-
Locate Tomcat access logsFind the Tomcat access log files on the UAA server. These are typically located in the Tomcat logs directory (commonly at $TOMCAT_HOME/logs or /var/vcap/sys/log/uaa/access_log.*). Identify files matching the access log pattern.Affected if Access log files exist and contain HTTP request records
-
Inspect logs for query parametersExamine the access log files for URL patterns that include query strings (content after '?' in the logged request path). Look specifically for URLs from authentication endpoints such as /oauth/authorize, /oauth/token, /login, or /uaa/login. Search for patterns like 'password=', 'client_secret=', 'code=', or 'access_token=' in the log entries.Affected if Query parameters appear in the access logs, especially for authentication-related endpoints
You are affected if your UAA version is below 74.8.0 (or Cf Deployment below 12.10.0) AND your Tomcat access logs contain query string parameters from authentication requests.
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 data12.10.074.8.0
Upgrade Cloud Foundry UAA Release to v74.8.0 or later to prevent query parameters from being logged, or implement log filtering to exclude sensitive query parameters if immediate upgrade is not feasible.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11290 — 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-11290 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