# CVE-2019-3781: CF CLI does not sanitize user's password in verbose/trace/debug

> Attackers with log access can view user passwords when verbose or debug modes are enabled in the Cloud Foundry CLI.

- **Severity:** High 8.2 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q96c-r8j3-g2qp, SUSE-SU-2019:1220-1, SUSE-SU-2019:1220-2

## What is CVE-2019-3781?

CVE-2019-3781 is a high-severity vulnerability in Cloud Foundry CF CLI, published on 7 Mar 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cloud Foundry CLI, versions prior to v6.43.0, improperly exposes passwords when verbose/trace/debugging is turned on. A local unauthenticated or remote authenticated malicious user with access to logs may gain part or all of a users password.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-215 (Insertion of Sensitive Information Into Debugging Code)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cf-cli` | SUSE:Linux Enterprise Module for CAP 15 | All versions | 6.43.0-3.3.2 |
| `cf-cli` | SUSE:Linux Enterprise Module for CAP 15 SP1 | All versions | 6.43.0-3.3.2 |

Products: Cloudfoundry Command Line Interface.

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

Upgrade to a fixed version.

## Is CVE-2019-3781 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3781 is a high-severity vulnerability in Cloud Foundry CF CLI, published on 7 Mar 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-3781 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-3781/ (Markdown: https://insights.sbomify.com/CVE-2019-3781/index.md)
```

## Sources

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

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