# CVE-2018-11045: Weak cryptography in Pivotal Operations Manager

> Attackers can predict the initial random number generator state by using a static seed file embedded in the appliance image, compromising cryptographic security.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2m5c-4ccv-xpr3

## What is CVE-2018-11045?

CVE-2018-11045 is a medium-severity vulnerability in Pivotal Operations Manager, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pivotal Operations Manager, versions 2.1 prior to 2.1.6 and 2.0 prior to 2.0.15 and 1.12 prior to 1.12.22, contains a static Linux Random Number Generator (LRNG) seed file embedded in the appliance image. An attacker with knowledge of the exact version and IaaS of a running OpsManager could get the contents of the corresponding seed from the published image and therefore infer the initial state of the LRNG.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Pivotal Software Operations Manager.

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

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

## Is CVE-2018-11045 being exploited?

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

## Other vulnerabilities in Pivotal Operations Manager

- [CVE-2016-0883](https://insights.sbomify.com/CVE-2016-0883/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-0897](https://insights.sbomify.com/CVE-2016-0897/): Security feature bypass in n/a (critical 9.8)
- [CVE-2018-15762](https://insights.sbomify.com/CVE-2018-15762/): Pivotal Operations Manager gives all users heightened privileges (critical 9.0)
- [CVE-2019-11292](https://insights.sbomify.com/CVE-2019-11292/): Pivotal Ops Manager logs query parameters in tomcat access file (high 8.8)
- [CVE-2018-11081](https://insights.sbomify.com/CVE-2018-11081/): Pivotal Operations Manager UAA config - temp Ram Disk (high 7.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11045 is a medium-severity vulnerability in Pivotal Operations Manager, published on 11 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11045 in the wild and no public exploit code.

Affected product: Pivotal Operations Manager. 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-11045/ (Markdown: https://insights.sbomify.com/CVE-2018-11045/index.md)
```

## Sources

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

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