Bosh Deployment logs leak sensitive information

published 2019-06-18 7y ago modified 2026-06-17 4mo ago also EUVD-2019-2960

cvss: 6.0; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits: 0; none known

Cloud Foundry BOSH 270.x versions prior to v270.1.1, contain a BOSH Director that does not properly redact credentials when configured to use a MySQL database. A local authenticated malicious user may read any credentials that are contained in a BOSH manifest.

Patch / fix

fixed in 1

Cloud Foundry BOSH v270.1.1

Is CVE-2019-11271 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

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

CVSS scores

assigned by	version	score	vector
CNA	3.0	6.0	CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

Cloud Foundry BOSH

Classification

Weakness

CWE-532 Insertion of Sensitive Information into Log File
CWE-522 Insufficiently Protected Credentials

References

cloudfoundry.org /blog/cve-2019-11271
vendor-advisory

Sources

CVE List CVE-2019-11271
NVD CVE-2019-11271

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.