CVE-2019-3781
CF CLI does not sanitize user's password in verbose/trace/debug
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.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
8.2
CF CLI does not sanitize user's password in verbose/trace/debug
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.
- Record
CVE-2019-3781- CVSS 3.0
- 8.2 High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - Weakness
- CWE-215
- Updated
- 2026-11-02
EUVDEUVD-2019-13412
8.2
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.
- Record
EUVD-2019-13412- CVSS 3.0
- 8.2 High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-q96c-r8j3-g2qp
8.8
Cloud Foundry CLI, versions prior to v6.43.0, improperly exposes passwords when verbose/trace...
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.
- Record
GHSA-q96c-r8j3-g2qp- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-200
- Updated
- 2026-11-02
NVD
8.8
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.
- Record
CVE-2019-3781- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - CVSS 3.0
- 8.2 High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N - CVSS 2.0
- 3.5 Low
AV:N/AC:M/Au:S/C:P/I:N/A:N - Weakness
- CWE-215, CWE-200
- Updated
- 2026-11-02
OSV
8.8
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.
- Record
CVE-2019-3781- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVSUSE-SU-2019:1220-1 No score
Security update for cf-cli
This update for cf-cli fixes the following issues:
cf-cli was updated: to version 6.43.0 (bsc#1132242)
Enhancements :
cf curlsupports a new--failflag (primarily for scripting purposes) which returns exit code22for server errors story- Improves
cf delete-orphaned-routessuch that it uses a different endpoint, reducing the chance of a race condition when two users are simultaneously deleting orphaned routes and associating routes with applications story - we've improved the speed of cf services - it now hits a single endpoint instead of making individual API calls
Security:
- CVE-2019-3781: CF CLI does not sanitize user’s password in verbose/trace/debug.
- Fixes issue with running cf login in verbose mode whereby passwords which contains regex were not completely redacted
- Fixes issue whilst running commands in verbose mode refresh tokens were not completely redacted
Other Bug Fixes:
- Updates help text for cf curlstory
- Now refresh tokens work properly whilst using cf curl with V3 CC API endpoints story
- Fixes performance degradation for cf services story
- cf delete-service requires that you are targeting a space story
- cf enable-service access for a service in an org will succeed if you have already enabled access for that service in that org story
cf-cli was updated to version 6.42.0:
Minor Enhancements:
- updated
cf restagehelp text and the first line in the command's output to indicate that using this command will cause app downtime story - updated the
cf bind-route-servicehelp text to clarify usage instructions story - improved an error message for
cf create-service-bokerto be more helpful when the CC API returns a502due to an invalid service broker catalog - upgraded to Golang 1.11.4 story
- added a short name
ueforcf unset-envstory - updated
cf marketplacecommand to include a newbrokercolumn to prepare for a upcoming services-related feature which will allow services to have the same name as long as they are associated with different service brokers story
Bugs:
- fix for
cf enable-service-access -p planwhereby when we refactored the code in CLIv6.41.0it created service plan visibilities as part of a subsequent run of the command (the unrefactored code skipped creating the service plan visibilities); now the command will skip creating service plan visibilities as it did prior to the refactor story - updated the
cf rename-buildpackhelp text which was missing reference to the-sstack flag story - updated help text for when users use
brew search cloudfoundry-clistory - now when you run
cf service service-instancefor a route service, the route service url appears in the key value table story
Update to version 6.41.0:
Enhancements:
- updated
cf --helpto include thedeletecommand story
Update to version 6.40.1:
Bug Fixes:
- Updates the minimum version for the buildpacks-stacks association feature. In CLI v6.39.0, when the feature was released, we incorrectly set the minimum to cc api version as
2.114. The minimum cc api version is now correctly set to2.112. story - Fixes a bug with inspecting a service…
- Record
SUSE-SU-2019:1220-1- Updated
- 2026-11-02
OSVSUSE-SU-2019:1220-2 No score
Security update for cf-cli
This update for cf-cli fixes the following issues:
cf-cli was updated: to version 6.43.0 (bsc#1132242)
Enhancements :
cf curlsupports a new--failflag (primarily for scripting purposes) which returns exit code22for server errors story- Improves
cf delete-orphaned-routessuch that it uses a different endpoint, reducing the chance of a race condition when two users are simultaneously deleting orphaned routes and associating routes with applications story - we've improved the speed of cf services - it now hits a single endpoint instead of making individual API calls
Security:
- CVE-2019-3781: CF CLI does not sanitize user’s password in verbose/trace/debug.
- Fixes issue with running cf login in verbose mode whereby passwords which contains regex were not completely redacted
- Fixes issue whilst running commands in verbose mode refresh tokens were not completely redacted
Other Bug Fixes:
- Updates help text for cf curlstory
- Now refresh tokens work properly whilst using cf curl with V3 CC API endpoints story
- Fixes performance degradation for cf services story
- cf delete-service requires that you are targeting a space story
- cf enable-service access for a service in an org will succeed if you have already enabled access for that service in that org story
cf-cli was updated to version 6.42.0:
Minor Enhancements:
- updated
cf restagehelp text and the first line in the command's output to indicate that using this command will cause app downtime story - updated the
cf bind-route-servicehelp text to clarify usage instructions story - improved an error message for
cf create-service-bokerto be more helpful when the CC API returns a502due to an invalid service broker catalog - upgraded to Golang 1.11.4 story
- added a short name
ueforcf unset-envstory - updated
cf marketplacecommand to include a newbrokercolumn to prepare for a upcoming services-related feature which will allow services to have the same name as long as they are associated with different service brokers story
Bugs:
- fix for
cf enable-service-access -p planwhereby when we refactored the code in CLIv6.41.0it created service plan visibilities as part of a subsequent run of the command (the unrefactored code skipped creating the service plan visibilities); now the command will skip creating service plan visibilities as it did prior to the refactor story - updated the
cf rename-buildpackhelp text which was missing reference to the-sstack flag story - updated help text for when users use
brew search cloudfoundry-clistory - now when you run
cf service service-instancefor a route service, the route service url appears in the key value table story
Update to version 6.41.0:
Enhancements:
- updated
cf --helpto include thedeletecommand story
Update to version 6.40.1:
Bug Fixes:
- Updates the minimum version for the buildpacks-stacks association feature. In CLI v6.39.0, when the feature was released, we incorrectly set the minimum to cc api version as
2.114. The minimum cc api version is now correctly set to2.112. story - Fixes a bug with inspecting a service…
- Record
SUSE-SU-2019:1220-2- Updated
- 2026-11-02
Affected products
Affected packages
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2019-3781 is a high vulnerability (CVSS 8.2) in Cloud Foundry Cf Cli, published March 7, 2019. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.33%, the 71st percentile. Fixed in cf-cli 6.43.0-3.3.2.
References
securityfocus.com/bid/107365
cloudfoundry.org/blog/cve-2019-3781
nvd.nist.gov/vuln/detail/CVE-2019-3781
github.com/advisories/GHSA-q96c-r8j3-g2qp
suse.com/support/update/announcement/2019/suse-su-20191220-1
bugzilla.suse.com/1132242
suse.com/security/cve/CVE-2019-3781
suse.com/support/update/announcement/2019/suse-su-20191220-2
Left out here: the rest of 2 source descriptions. The JSON record has them.