# CVE-2019-3800: CF CLI writes the client id and secret to config file

> Local attackers can read client credentials from the CF CLI config file to impersonate the client and access Cloud Foundry resources.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2wpx-p7qg-954w

## What is CVE-2019-3800?

CVE-2019-3800 is a medium-severity vulnerability in Cloud Foundry CF CLI, published on 5 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CF CLI version prior to v6.45.0 (bosh release version 1.16.0) writes the client id and secret to its config file when the user authenticates with --client-credentials flag. A local authenticated malicious user with access to the CF CLI config file can act as that client, who is the owner of the leaked credentials.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-522 (Insufficiently Protected Credentials)

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

It affects 55 products.


Products: Anynines Elasticsearch, Anynines Logme, Anynines Mongodb, Anynines Mysql, Anynines Postgresql, Anynines Rabbitmq, Anynines Redis, Apigee Edge Service Broker, Appdynamics Application Analytics, Appdynamics Application Performance Monitoring, Appdynamics Platform Montioring, Bluemedora Nozzle, Contrastsecurity Service Broker, Cyberark Conjur Service Broker, Datadoghq Application Monitoring, Datastax Enterprise Service Broker, Dynatrace Service Broker, Forgerock Service Broker, Google Google Cloud Platform Service Broker, Ibm Websphere Liberty  and 35 more.

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

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

## Is CVE-2019-3800 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3800 is a medium-severity vulnerability in Cloud Foundry CF CLI, published on 5 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3800 in the wild and no public exploit code.

Affected product: Cloud Foundry CF CLI. 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-3800/ (Markdown: https://insights.sbomify.com/CVE-2019-3800/index.md)
```

## Sources

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

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