dbcve.org
Command Line InterfaceApplication · Cloudfoundry

CVE-2019-3781

HIGH · 8.8 CVSS v3.1 Published 2019-03-07
Fix available
A fix is available. Upgrade to 6.43.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
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.

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 confidence

The Cloud Foundry CLI versions prior to v6.43.0 improperly expose user passwords in verbose, trace, or debug output. When debugging flags are enabled, credentials are written to logs in plaintext or partially readable form, allowing attackers with log access to recover password characters.

MitigationUpgrade Cloud Foundry CLI to version v6.43.0 or later to prevent credential exposure in logs.

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
Command Line InterfaceApplication
Affected:< 6.43.0

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Cloud Foundry CLI version
    Run `cf version` or `cf --version` to determine the installed CLI version
    Affected if The installed version is less than 6.43.0
  2. Identify debugging flags in use
    Review command history, shell profiles, and environment variables for flags such as `-v`, `--verbose`, `-t`, `--trace`, or `-d`, `--debug` used with cf commands
    Affected if Debugging, verbose, or trace flags are enabled or commonly used with cf CLI commands
  3. Examine log files for credential exposure
    Inspect cf CLI output logs, terminal session logs, or application logs generated while running cf commands with debugging flags enabled
    Affected if Log files contain plaintext or partially readable password characters from cf CLI operations
  4. Review environment configuration
    Check for environment variables or configuration files that enable trace or debug mode for the cf CLI (such as CF_TRACE=true)
    Affected if CF_TRACE or similar debugging environment variables are set

The environment is affected if the Cloud Foundry CLI version is below 6.43.0 AND debugging/verbose flags are or were enabled, resulting in credentials being written to accessible logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 6.43.0 or later
Fixed in 6.43.0
Interim mitigation

Upgrade Cloud Foundry CLI to version v6.43.0 or later to prevent credential exposure in logs.

Fix this in Command Line Interface Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3781 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-3781 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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