# CVE-2018-15800: Timing attack allows extraction of signing key in Bits Service

> Attackers can extract the signing key via timing attacks to gain full read and write access to Bits Service storage.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 10 Dec 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wxfx-g5v8-gmxf

## What is CVE-2018-15800?

CVE-2018-15800 is a high-severity vulnerability in Cloud Foundry Bits Service Release, published on 10 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cloud Foundry Bits Service, versions prior to 2.18.0, includes an information disclosure vulnerability. A remote malicious user may execute a timing attack to brute-force the signing key, allowing them complete read and write access to the the Bits Service storage.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cloud Foundry Bits Service.

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

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

## Is CVE-2018-15800 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15800 is a high-severity vulnerability in Cloud Foundry Bits Service Release, published on 10 Dec 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-15800 in the wild and no public exploit code.

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

## Sources

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

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