Pivotal Operations Manager gives all users heightened privileges

published 2018-11-02 8y ago modified 2026-06-17 4mo ago also EUVD-2018-7625

cvss: 9.0; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

Pivotal Cloud Foundry Pivotal Operations Manager 2.0.24, 2.1.15, 2.2.7, 2.3.1

Is CVE-2018-15762 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	9.0	CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

Pivotal Cloud Foundry Pivotal Operations Manager

Classification

Weakness

CWE-269 Improper Privilege Management

References

pivotal.io /security/cve-2018-15762
vendor-advisory

Sources

CVE List CVE-2018-15762
NVD CVE-2018-15762

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.