MongoDB Ops Manager: Improper Privilege Management
CVE-2023-4009 is a high-severity improper privilege management vulnerability in MongoDB Ops Manager from MongoDB, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists versions 6.0.17, 5.0.22 as the first without the flaw, so updating MongoDB Ops Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.76% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update MongoDB Ops Manager to 6.0.17 or 5.0.22, whichever matches your release line, or a later version.
- Update Ops Manager Server to 5.0.22 or 6.0.17, whichever matches your release line, or a later version.
- Read the advisory on mongodb.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MongoDB | MongoDB Ops Manager | 6.0 up to, but not including, 6.0.17; 5.0 up to, but not including, 5.0.22 | 6.0.17, 5.0.22 |
| MongoDB | Ops Manager Server | 5.0.0 up to, but not including, 5.0.22; 6.0.0 up to, but not including, 6.0.17 | 5.0.22, 6.0.17 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.2 | High | CNA (mongodb.com) |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
In MongoDB Ops Manager v5.0 prior to 5.0.22 and v6.0 prior to 6.0.17 it is possible for an authenticated user with project owner or project user admin access to generate an API key with the privileges of org owner resulting in privilege escalation.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Recent Improper Privilege Management vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.