dbcve.org
MongoDBDatabase / datastore

CVE-2024-1351

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 4.4.29 / 5.0.25 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which may result in untrusted connections to succeed. This may effectively reduce the security guarantees provided by TLS and open connections that should have been closed due to failing certificate validation. This issue affects MongoDB Server v7.0 versions prior to and including 7.0.5, MongoDB Server v6.0 versions prior to and including 6.0.13, MongoDB Server v5.0 versions prior to and including 5.0.24 and MongoDB Server v4.4 versions prior to and including 4.4.28. Required Configuration : A server process will allow incoming connections to skip peer certificate validation if the server process was started with TLS enabled (net.tls.mode set to allowTLS, preferTLS, or requireTLS) and without a net.tls.CAFile configured.

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
How this class of weakness works · CWE-295

The application does not properly validate the TLS certificate presented by the other side — skipping the chain, the hostname, or expiry — so an attacker with a forged or mismatched certificate can sit in the middle of a supposedly secure connection. It is a common trap in custom clients and misconfigured libraries. The fix is full certificate validation, and never disabling verification to make errors go away.

General guidance for the improper certificate validation class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
MongoDBDatabase / datastore
Affected:>= 4.4.0, < 4.4.29>= 5.0.0, < 5.0.25>= 6.0.0, < 6.0.14>= 7.0.0, < 7.0.6
Astra Control CenterApplication
Affected:all versions
Ontap ToolsApplication
Affected:= 10

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 · scoped
Upgrade available Upgrade to 4.4.29 / 5.0.25 / 6.0.14 or later
Fixed in 4.4.295.0.256.0.14
Vendor patch jira.mongodb.org →
Recommended fix High confidence

Upgrade to MongoDB 4.4.29, 5.0.25, 6.0.14, or 7.0.6 depending on your current major version branch

  1. 1. Identify the current MongoDB Server version by running: db.version() or mongod --version
  2. 2. Based on the current major version, plan upgrade to the corresponding fixed release: 4.4.29 for 4.4.x, 5.0.25 for 5.0.x, 6.0.14 for 6.0.x, or 7.0.6 for 7.0.x
  3. 3. Create a full backup of all databases before upgrading
  4. 4. Stop the MongoDB Server process
  5. 5. Install the appropriate fixed version of MongoDB Server for your major version branch
  6. 6. Start the MongoDB Server with the fixed version
  7. 7. Verify peer certificate validation is working by ensuring net.tls.CAFile is configured in the configuration file (mongod.conf) or via command line with --tlsCAFile pointing to a valid CA certificate file
  8. 8. Test TLS connections to confirm certificate validation is enforced
Caveat Review MongoDB upgrade documentation for your version path; always test in staging first; ensure client TLS configurations remain compatible

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1351 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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