CVE-2019-11293
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.10.0, when set to logging level DEBUG, logs client_secret credentials when sent as a query parameter. A remote authenticated malicious user could gain access to user credentials via the uaa.log file if authentication is provided via query parameters.
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 confidenceThe Cloud Foundry UAA (User Account and Authentication) server logs client_secret credentials in plaintext when DEBUG logging level is enabled and credentials are passed as query parameters during authentication. An authenticated malicious user with access to the uaa.log file can extract these credentials and gain unauthorized access.
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.12.0< 74.10.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine UAA versionCheck the installed version of Cloud Foundry User Account and Authentication (UAA) by reviewing the UAA release manifest or running 'uaac version'. Compare against the affected threshold of 74.10.0.Affected if The installed UAA version is below 74.10.0.
-
Determine Cf Deployment versionCheck the Cloud Foundry deployment version via the deployment manifest or 'cf target' output. Compare against the affected threshold of 12.12.0.Affected if The installed Cf Deployment version is below 12.12.0.
-
Verify logging configurationInspect the UAA logging configuration (typically in log4j or logback configuration files) to determine if the DEBUG log level is enabled for the authentication module.Affected if DEBUG logging level is enabled for UAA authentication components.
-
Inspect authentication methodReview the authentication configuration or client application setup to determine whether client_secret credentials are passed as query parameters in the URL rather than using form POST body parameters.Affected if Authentication requests transmit client_secret via URL query parameters.
-
Examine uaa.log for plaintext secretsSearch the uaa.log file for instances of client_secret values appearing in plaintext. Use grep or a log analysis tool to look for patterns where secret values are logged during authentication flows.Affected if Plaintext client_secret credentials are present in the uaa.log file.
A user is affected if their environment runs a UAA version below 74.10.0 (or Cf Deployment below 12.12.0) AND has DEBUG logging enabled AND uses query parameter-based authentication, resulting in plaintext secrets in logs.
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.12.074.10.0
Upgrade to UAA Release v74.10.0 or later, and/or ensure authentication uses form POST instead of query parameters while setting logging level to INFO or higher.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11293 — 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-11293 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