Ops Manager ServerApplication · MongoDB
CVE-2023-0342
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 · uneditedMongoDB Ops Manager Diagnostics Archive may not redact sensitive PEM key file password app settings. Archives do not include the PEM files themselves. This issue affects MongoDB Ops Manager v5.0 prior to 5.0.21 and MongoDB Ops Manager v6.0 prior to 6.0.12
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 confidenceMongoDB Ops Manager diagnostics archives fail to redact sensitive PEM key file passwords from app settings before packaging the archive for support/troubleshooting. While the actual PEM files are not included in archives, the unredacted password values represent a confidentiality issue for sensitive key material.
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 Manager ServerApplication
>= 5.0.0, < 5.0.21>= 6.0.0, < 6.0.12CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check Ops Manager versionDetermine the installed version of MongoDB Ops Manager Server through the Ops Manager UI or APIAffected if Version is >= 5.0.0 and < 5.0.21, or >= 6.0.0 and < 6.0.12
-
Locate diagnostic archivesFind diagnostics archives generated by Ops Manager for support or troubleshooting purposes, typically stored in designated log or support directoriesAffected if Diagnostic archives were created by an affected version of Ops Manager
-
Inspect archive app settingsExamine the app settings configuration files within the diagnostic archive for PEM key file password fieldsAffected if Password values for PEM key files appear unredacted (visible as plain text) rather than masked or removed in the archived app settings
A user is affected if Ops Manager version falls within the vulnerable ranges AND diagnostic archives containing app settings with unredacted PEM key file passwords were generated and are accessible.
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.
dbcve · scoped5.0.216.0.12
Upgrade MongoDB Ops Manager to v5.0.21 or later, or v6.0.12 or later to ensure diagnostics archives properly redact PEM key file passwords from exported app settings.
Ops Manager 5.0.21 or Ops Manager 6.0.12 (depending on your current major version)
- 1. Back up your current MongoDB Ops Manager installation and database
- 2. Download the fixed version of Ops Manager (5.0.21 for 5.x users or 6.0.12 for 6.x users) from the MongoDB downloads page
- 3. Stop the Ops Manager application service
- 4. Install the new Ops Manager version following the standard upgrade procedure
- 5. Verify the diagnostic archive functionality no longer exposes PEM key file passwords
- 6. Restart the Ops Manager service
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ops Manager Server
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0342 — 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-2023-0342 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