Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2018-15762: Pivotal Operations Manager, versions 2.0.x prior to 2.0.24, versions 2.1.x prior to 2.1.15, versions 2.2.x pri

48
This month
CRITICAL 9.0UPGRADE

CVE-2018-15762 is a critical-severity flaw (CVSS 9.0) 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.0.x prior to 2.0.24, versions 2.1.x prior to 2.1.15, versions 2.2.x prior to 2.2.7, and versions 2.3.x prior to 2.3.1, grants all users a scope which allows for privilege escalation. A remote malicious user who has been authenticated may create a new client with administrator privileges for Opsman.

Why this priority

  • Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score9.0 (Critical)
Attack vectorAdjacent network
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance1.1% (top 35%)
CISA exploited listNo
WeaknessCWE-269
Published2018-11-02
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: >= 2.0.0 and < 2.0.24 · >= 2.1.0 and < 2.1.15 · >= 2.2.0 and < 2.2.7 · >= 2.3.0 and < 2.3.1
Fixed in: 2.0.24, 2.1.15, 2.2.7, 2.3.1
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy operations-manager || rpm -q operations-manager || operations-manager --version
2. UPGRADE to 2.0.24 (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 2.0.0 (Debian / Ubuntu)
apt-cache madison operations-manager sudo apt install operations-manager=<VERSION_BEFORE_2.0.0> 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_2.0.0> 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-15762?

operations manager: upgrade to 2.0.24, 2.1.15, 2.2.7, 2.3.1. Exact commands for each OS are on this page.

Is CVE-2018-15762 being exploited?

CVE-2018-15762 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-15762 affect?

CVE-2018-15762 affects operations manager. Severity is critical (CVSS 9.0). Pivotal Operations Manager, versions 2.0.x prior to 2.0.24, versions 2.1.x prior to 2.1.15, versions 2.2.x prior to 2.2.7, and versions 2.3.x prior to 2.3.1, grants all users a scope which allows for privilege escalation. A remote malicious

How urgent is CVE-2018-15762?

Priority 48/100. Critical severity

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.