Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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, con

40
This month
MEDIUM 5.9REMOTEUPGRADE

CVE-2018-11045 is a medium-severity flaw (CVSS 5.9) affecting operations manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.9% (top 42%)
CISA exploited listNo
WeaknessCWE-330
Published2018-07-11
Last modified2026-06-17
Publisher (CNA): Dell · Vendor: pivotal software

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

pivotal software operations manager UPGRADE
Affected: >= 1.12 and < 1.12.22 · > 2.0 and < 2.0.15 · >= 2.1.0 and < 2.1.6
Fixed in: 1.12.22, 2.0.15, 2.1.6
Safe to downgrade to: a release before 1.12
1. Check installed version
apt-cache policy operations-manager || rpm -q operations-manager || operations-manager --version
2. UPGRADE to 1.12.22 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade operations-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade operations-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.12 (Debian / Ubuntu)
apt-cache madison operations-manager sudo apt install operations-manager=<VERSION_BEFORE_1.12> sudo apt-mark hold operations-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list operations-manager sudo dnf downgrade operations-manager-<VERSION_BEFORE_1.12> sudo dnf versionlock add operations-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-11045?

operations manager: upgrade to 1.12.22, 2.0.15, 2.1.6. Exact commands for each OS are on this page.

Is CVE-2018-11045 being exploited?

CVE-2018-11045 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-11045 affect?

CVE-2018-11045 affects operations manager. Severity is medium (CVSS 5.9). 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 e

How urgent is CVE-2018-11045?

Priority 40/100. Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.