CVE-2018-1264
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 Log Cache, versions prior to 1.1.1, logs its UAA client secret on startup as part of its envstruct report. A remote attacker who has gained access to the Log Cache VM can read this secret, gaining all privileges held by the Log Cache UAA client. In the worst case, if this client is an admin, the attacker would gain complete control over the Foundation.
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 confidenceCloud Foundry Log Cache versions prior to 1.1.1 log their UAA client secret in plaintext during startup as part of an envstruct report. Any attacker who has compromised access to the Log Cache VM can read this secret from the logs and authenticate as the Log Cache UAA client, potentially gaining admin-level access to the entire foundation.
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.1.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 if Log Cache is deployedLocate the log-cache process, service, or installation directory in your Cloud Foundry environment. Check for processes named 'log-cache' or service definitions referencing Log Cache.Affected if Log Cache is not installed or not present in the environment
-
Determine Log Cache versionRun 'log-cache --version' or check the installed package version using your deployment manifest or package manager. Compare the version number against the affected range (anything below 1.1.1).Affected if The installed version is 1.1.0 or lower (any version prior to 1.1.1)
-
Examine startup logs for plaintext secretsReview Log Cache startup logs (typically found in /var/vcap/sys/log/log-cache/ or systemd journal for the log-cache service). Search for the UAA client secret appearing in plain text rather than masked or redacted.Affected if The UAA client secret is visible in plaintext within the startup logs
-
Locate envstruct report in logsSearch Log Cache logs for the string 'envstruct' or structured environment variable reports generated during startup. This report format is where the credential leakage occurs.Affected if An envstruct report is present in the logs and contains the UAA client secret in plaintext
You are affected if Log Cache version is below 1.1.1 AND plaintext UAA client credentials appear in startup logs or envstruct output.
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.
dbcve · scoped1.1.1
Upgrade Log Cache to version 1.1.1 or later to prevent credential leakage. Immediately rotate any exposed UAA client credentials as a precautionary measure.
1.1.1
- Upgrade Cloud Foundry Log Cache to version 1.1.1 or later to resolve the UAA client secret being logged in the envstruct report on startup
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1264 — 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-1264 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