CVE-2018-15762
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPivotal 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePivotal Operations Manager contains an insecure direct object reference or authorization flaw where an OAuth scope incorrectly grants all authenticated users the ability to create new clients with administrator privileges, enabling vertical privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0.0, < 2.0.24>= 2.1.0, < 2.1.15>= 2.2.0, < 2.2.7>= 2.3.0, < 2.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine Operations Manager versionLog in to the Pivotal Operations Manager web interface and check the version displayed in the product header or footer. Alternatively, access the Ops Manager API at /api/v0/info or check the installed product stemcell information.Affected if The installed version falls within any of these ranges: 2.0.0 to 2.0.23, 2.1.0 to 2.1.14, 2.2.0 to 2.2.6, or 2.3.0.
-
Verify UAA/OAuth is in useConfirm that the User Account and Authentication (UAA) server is enabled and configured in the Operations Manager deployment. Check the deployed tile configurations for UAA presence.Affected if UAA is enabled and user authentication is configured through it.
-
Inspect OAuth client configurationAccess the UAA API endpoint /oauth/clients or use the UAA CLI (uaac) to list registered OAuth clients. Query for clients that have the scope 'ops.admin' or administrator-level authorities granted.Affected if Any authenticated user can successfully call the client registration endpoint and obtain admin-level privileges without proper authorization checks.
-
Check for unauthorized admin clientsReview the OAuth client registrations in UAA. Look for any client applications that were created with administrator privileges (clients with ops.admin scope or admin authority) that were not intentionally provisioned by the administrator.Affected if Non-administrator users have the ability to create clients with elevated (admin) privileges through the OAuth authorization server.
You are affected if your Operations Manager version is 2.0.0-2.0.23, 2.1.0-2.1.14, 2.2.0-2.2.6, or 2.3.0 AND the UAA OAuth service is enabled, allowing any authenticated user to escalate privileges via client creation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.0.242.1.152.2.7
Upgrade Pivotal Operations Manager to version 2.0.24, 2.1.15, 2.2.7, or 2.3.1 or later to remediate the improper scope assignment.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-15762 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data