Ops ManagerApplication · MongoDB
CVE-2020-7927
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 · uneditedSpecially crafted API calls may allow an authenticated user who holds Organization Owner privilege to obtain an API key with Global Role privilege. This issue affects MongoDB Ops Manager v4.2 versions prior to and including 4.2.17, MongoDB Ops Manager v4.3 versions prior to and including 4.3.9 and MongoDB Ops Manager v4.4 versions prior to and including 4.4.2.
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 confidenceA privilege escalation vulnerability in MongoDB Ops Manager allows an authenticated user with Organization Owner privileges to obtain an API key with Global Role privileges through specially crafted API calls. This elevates the user's permissions from organization-level to system-wide administrative access.
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
Ops ManagerApplication
>= 4.2.0, <= 4.2.17>= 4.3.0, <= 4.3.9>= 4.4.0, <= 4.4.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify Ops Manager versionCheck the Ops Manager version by accessing the System Overview page in the Ops Manager UI, or query the application database: db.getSiblingDB('admin').system.version.findOne({_id: 'version'}). Note the exact version number.Affected if The installed version falls within 4.2.0 to 4.2.17, 4.3.0 to 4.3.9, or 4.4.0 to 4.4.2.
-
Identify users with Organization Owner roleIn Ops Manager UI, navigate to the Organization settings and review the list of users assigned the Organization Owner role. Document all accounts with this privilege level.Affected if Any user with Organization Owner role exists in the organization.
-
Review API keys with Global Admin roleNavigate to the global API Keys section in Ops Manager (Organization > All Projects > API Keys, or query the appdb: db.getSiblingDB('admin').system.users.find({'roles.role': 'GLOBAL_ADMIN'})). List all API keys that have GLOBAL_ADMIN or GLOBAL_OWNER roles.Affected if There are API keys assigned GLOBAL_ADMIN or GLOBAL_OWNER roles that were not created by existing GLOBAL_OWNER administrators.
-
Cross-reference API key creation with Organization OwnersReview the audit logs or API key creation history to identify if any Organization Owner user created or requested API keys with Global role privileges. Check audit logs for events involving apiKeys/create with GLOBAL_ROLE permissions.Affected if API keys with Global roles were created or modified after the account was granted Organization Owner status, without explicit GLOBAL_OWNER approval.
A user is affected if their Ops Manager version is within the affected ranges AND an Organization Owner has obtained API keys with Global role privileges without proper authorization from a Global Administrator.
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 dataUpgrade MongoDB Ops Manager to version 4.2.18 or later, 4.3.10 or later, or 4.4.3 or later to obtain the patch for this vulnerability.
Fix this in Ops Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7927 — 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-2020-7927 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