CVE-2018-15797
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 · uneditedCloud Foundry NFS volume release, 1.2.x prior to 1.2.5, 1.5.x prior to 1.5.4, 1.7.x prior to 1.7.3, logs the cf admin username and password when running the nfsbrokerpush BOSH deploy errand. A remote authenticated user with access to BOSH can obtain the admin credentials for the Cloud Foundry Platform through the logs of the NFS volume deploy errand.
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 confidenceThe NFS volume release's nfsbrokerpush BOSH errand logs Cloud Foundry admin credentials (username and password) in plaintext to deployment logs. An authenticated user with BOSH access can read these logs and obtain the admin credentials for the Cloud Foundry platform.
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>= 1.2.0, < 1.2.5>= 1.5.0, < 1.5.4>= 1.7.0, < 1.7.3CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed NFS volume release versionUse 'bosh deployments' or check your deployment manifest to find the version of the nfs-volume-release. Compare this version against the affected ranges: 1.2.0 to before 1.2.5, 1.5.0 to before 1.5.4, or 1.7.0 to before 1.7.3.Affected if The installed version falls within any of the affected version ranges (>=1.2.0 <1.2.5, >=1.5.0 <1.5.4, or >=1.7.0 <1.7.3).
-
Locate nfsbrokerpush errand logsAccess your BOSH task logs or deployment logs. The nfsbrokerpush is a BOSH errand that runs as part of the NFS volume release deployment. Use 'bosh tasks --recent' to find the task ID, then 'bosh task <ID>' to view logs.Affected if You can locate nfsbrokerpush errand logs from any deployment of the affected NFS volume release versions.
-
Search logs for plaintext credentialsExamine the nfsbrokerpush errand logs for plaintext strings that resemble Cloud Foundry admin credentials. Look for patterns including 'username', 'password', 'admin', or credential values in cleartext.Affected if The logs contain plaintext username and password strings, indicating admin credentials were logged.
-
Review BOSH credential configurationCheck the deployment manifest or variables file for the Cloud Foundry admin credentials configured for the nfsbrokerpush errand. These credentials are passed as properties to the errand.Affected if The deployment uses explicit admin credentials configured for the NFS broker that could have been logged.
You are affected if you deployed an NFS volume release version in the affected ranges AND the nfsbrokerpush errand logs from your deployment contain plaintext admin credentials.
Generated from the published advisory. Verify against your own configuration.
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 data1.2.51.5.41.7.3
Upgrade NFS volume release to version 1.2.5, 1.5.4, or 1.7.3 or later to eliminate credential logging. Additionally, rotate any Cloud Foundry admin credentials that may have been exposed in the logs.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-15797 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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