NVD / CVE Program· CNA dell

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

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 2% (FIRST EPSS); higher than 81.5% of all records.
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.0—No exploit No fix recorded

Info leak

Published: Aug 5, 2019
Updated: Jun 16, 2026
EPSS: 2.0% · 81th percentile
CWE: CWE-522

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 2.0%

CNA vs NVD score

NVD: 7.8
CNA · dell: 6.3; 1.5 point gap

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
pivotal	cloud foundry command line interface	cpe:2.3:a:pivotal:cloud_foundry_command_line_interface
pivotal	cloud foundry command line interface release	cpe:2.3:a:pivotal:cloud_foundry_command_line_interface_release
pivotal	cloud foundry deployment	cpe:2.3:a:pivotal:cloud_foundry_deployment
pivotal	cloud foundry deployment concourse tasks	cpe:2.3:a:pivotal:cloud_foundry_deployment_concourse_tasks
pivotal	cloud foundry log cache release	cpe:2.3:a:pivotal:cloud_foundry_log_cache_release
pivotal	cloud foundry networking release	cpe:2.3:a:pivotal:cloud_foundry_networking_release
pivotal	cloud foundry notifications	cpe:2.3:a:pivotal:cloud_foundry_notifications
pivotal	cloud foundry routing release	cpe:2.3:a:pivotal:cloud_foundry_routing_release
pivotal	cloud foundry smoke test	cpe:2.3:a:pivotal:cloud_foundry_smoke_test
pivotal	application service	cpe:2.3:a:pivotal:application_service
pivotal	cloud foundry autoscaling release	cpe:2.3:a:pivotal:cloud_foundry_autoscaling_release
pivotal	cloud foundry event alerts	cpe:2.3:a:pivotal:cloud_foundry_event_alerts

and 43 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

anynines elasticsearchbefore 2.1.2
anynines logmebefore 2.1.2
anynines mongodbbefore 2.1.2
anynines mysqlbefore 2.1.2
anynines postgresqlbefore 2.1.2
anynines rabbitmqbefore 2.1.2
anynines redisbefore 2.1.2
apigee edge service brokerbefore 3.1.3
appdynamics application analyticsbefore 4.7.652
appdynamics application performance monitoringbefore 4.6.64
appdynamics platform montioringbefore 4.7.712
bluemedora nozzlebefore 3.1.1
contrastsecurity service brokerbefore 2.2.0
cyberark conjur service brokerbefore 1.1.1
datadoghq application monitoringbefore 1.7.0
datastax enterprise service brokerbefore 1.0.2
dynatrace service brokerbefore 1.4.2
forgerock service brokerbefore 2.1.2
google google cloud platform service brokerbefore 4.2.3
ibm websphere liberty before 3.11.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.

Cloud Foundry CF CLI
- versions prior to v6.45.0affected
Cloud Foundry CF CLI Release
- v1.x before v1.16.0affected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-522 · Insufficiently Protected Credentials

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

pivotal.io/security/cve-2019-3800

Show all references (1 more)

www.cloudfoundry.org/blog/cve-2019-3800

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records