# CVE-2019-11293: UAA logs all query parameters with debug logging level

> Attackers can read client secrets from logs if debug logging is enabled, exposing credentials to anyone with log access.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-75vm-6gpr-f398

## What is CVE-2019-11293?

CVE-2019-11293 is a high-severity vulnerability in Cloud Foundry UAA Release, published on 6 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cloud 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2019-11293?

It affects 2 products.


Products: Cloudfoundry Cf-Deployment, Cloudfoundry User Account and Authentication.

## How do I fix CVE-2019-11293?

No fix has been published for CVE-2019-11293 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-11293 being exploited?

There is no known exploitation of CVE-2019-11293 in the wild and no public exploit code.

## Other vulnerabilities in Cloud Foundry UAA Release

- [CVE-2022-31733](https://insights.sbomify.com/CVE-2022-31733/): Auth bypass in Cloud Foundry Diego and CF Deployment (critical 9.1)
- [CVE-2020-5402](https://insights.sbomify.com/CVE-2020-5402/): UAA fails to check the state parameter when authenticating with external IDPs (high 8.8)
- [CVE-2019-11290](https://insights.sbomify.com/CVE-2019-11290/): Cloud Foundry UAA logs query parameters in tomcat access file (high 8.8)
- [CVE-2019-11283](https://insights.sbomify.com/CVE-2019-11283/): Password leak in smbdriver logs (high 8.8)
- [CVE-2018-1191](https://insights.sbomify.com/CVE-2018-1191/): Information disclosure in Garden-runC (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11293 and fix it if it is affected.

What it is: CVE-2019-11293 is a high-severity vulnerability in Cloud Foundry UAA Release, published on 6 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11293 in the wild and no public exploit code.

Affected product: Cloud Foundry UAA Release. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11293/ (Markdown: https://insights.sbomify.com/CVE-2019-11293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11293
- OSV: https://osv.dev/vulnerability/CVE-2019-11293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11293/
Summaries are generated and may contain mistakes; the official description above is the record.