# CVE-2018-1223: Information disclosure in Container Runtime

> Attackers with log access can steal UAA and vCenter credentials from Cloud Foundry Container Runtime logs to escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gfwv-5245-24h8

## What is CVE-2018-1223?

CVE-2018-1223 is a high-severity vulnerability in Cloud Foundry Container Runtime, published on 17 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cloud Foundry Container Runtime (kubo-release), versions prior to 0.14.0, may leak UAA and vCenter credentials to application logs. A malicious user with the ability to read the application logs could use these credentials to escalate privileges.

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

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

It affects 1 product.


Products: Pivotal Cloud Foundry Container Runtime.

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

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

## Is CVE-2018-1223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1223 is a high-severity vulnerability in Cloud Foundry Container Runtime, published on 17 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1223 in the wild and no public exploit code.

Affected product: Cloud Foundry Container Runtime. 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-1223/ (Markdown: https://insights.sbomify.com/CVE-2018-1223/index.md)
```

## Sources

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

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