# CVE-2018-15795: CredHub Service Broker uses guessable client secret

> Attackers can guess the service broker's client secret to obtain or modify user credentials in Pivotal CredHub Service Broker.

- **Severity:** High 8.1 (`CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q3jg-4c82-j4xh

## What is CVE-2018-15795?

CVE-2018-15795 is a high-severity vulnerability in Pivotal Cloud Foundry CredHub Service Broker, published on 13 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pivotal CredHub Service Broker, versions prior to 1.1.0, uses a guessable form of random number generation in creating service broker's UAA client. A remote malicious user may guess the client secret and obtain or modify credentials for users of the CredHub Service.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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

2 open source packages ship an affected version, including org.springframework.credhub:spring-credhub-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.credhub:spring-credhub-core` | Maven | All versions | 1.1.0 |
| `org.springframework.credhub:spring-credhub-core` | Maven | All versions | 1.1.0 |

Products: Pivotal Software Credhub Service Broker.

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

Upgrade org.springframework.credhub:spring-credhub-core to 1.1.0 or later.

## Is CVE-2018-15795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-15795 is a high-severity vulnerability in Pivotal Cloud Foundry CredHub Service Broker, published on 13 Nov 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15795 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.credhub:spring-credhub-core (Maven): affected all versions; fixed in 1.1.0
- org.springframework.credhub:spring-credhub-core (Maven): affected all versions; fixed in 1.1.0

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-15795/ (Markdown: https://insights.sbomify.com/CVE-2018-15795/index.md)
```

## Sources

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

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