# CVE-2018-15796: Signing Key Extraction in Bits Service Release

> Attackers can extract signing keys from insecurely hashed URLs 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:** 9 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xx5w-cqxh-w2m4

## What is CVE-2018-15796?

CVE-2018-15796 is a high-severity vulnerability in Cloud Foundry bits-service-release, published on 9 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cloud Foundry Bits Service Release, versions prior to 2.14.0, uses an insecure hashing algorithm to sign URLs. A remote malicious user may obtain a signed URL and extract the signing key, allowing them complete read and write access to the the Bits Service storage.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 1 product.


Products: Pivotal Software Bits Service.

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

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

## Is CVE-2018-15796 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15796 is a high-severity vulnerability in Cloud Foundry bits-service-release, published on 9 Nov 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-15796 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-15796/ (Markdown: https://insights.sbomify.com/CVE-2018-15796/index.md)
```

## Sources

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

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