# CVE-2018-1264: Log Cache logs UAA client secret on startup

> An attacker with VM access can read the UAA client secret from startup logs, potentially gaining admin privileges over the Cloud Foundry foundation.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-829v-ph86-cw55

## What is CVE-2018-1264?

CVE-2018-1264 is a critical vulnerability in Cloud Foundry log-cache-release, published on 5 Oct 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cloud 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2018-1264?

It affects 1 product.


Products: Pivotal Software Cloud Foundry Log Cache.

## How do I fix CVE-2018-1264?

No fix has been published for CVE-2018-1264 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1264 being exploited?

There is no known exploitation of CVE-2018-1264 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1264 and fix it if it is affected.

What it is: CVE-2018-1264 is a critical vulnerability in Cloud Foundry log-cache-release, published on 5 Oct 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1264 in the wild and no public exploit code.

Affected product: Cloud Foundry log-cache-release. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1264/ (Markdown: https://insights.sbomify.com/CVE-2018-1264/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1264
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1264
- OSV: https://osv.dev/vulnerability/CVE-2018-1264

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1264/
Summaries are generated and may contain mistakes; the official description above is the record.