Skip to content
Fencer Intel
high 8.2

CVE-2019-3781 json

CF CLI does not sanitize user's password in verbose/trace/debug

published 7y ago modified 4mo ago also EUVD-2019-13412

cvss
8.2
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 71%
public exploits
0
none known

Summary

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.

Patch / fix

  • Cloud Foundry CF CLI v6.43.0
  • cf-cli SLE Module for CAP 15 SP1, SLE Module for CAP 15 6.43.0-3.3.2

suse advisories SUSE-SU-2019:1220-2SUSE-SU-2019:1220-1

Is CVE-2019-3781 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 8.2 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:P/I:N/A:N

Affected products

  • Cloud Foundry CF CLI

Classification

Weakness
  • CWE-215 Insertion of Sensitive Information Into Debugging Code
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.