dbcve.org
MongoDBDatabase / datastore

CVE-2023-1409

HIGH · 7.5 CVSS v3.1 Published 2023-08-23
Fix available
A fix is available. Upgrade to 4.4.23 / 6.0.7 or later.
See remediation →
84/100
Remediation priority · High
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
If the MongoDB Server running on Windows or macOS is configured to use TLS with a specific set of configuration options that are already known to work securely in other platforms (e.g. Linux), it is possible that client certificate validation may not be in effect, potentially allowing client to establish a TLS connection with the server that supplies any certificate. This issue affect all MongoDB Server v6.3 versions, MongoDB Server v5.0 versions v5.0.0 to v5.0.14 and all MongoDB Server v4.4 versions.

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.23>= 5.0.0, <= 5.0.14>= 6.0.0, < 6.0.7>= 6.3.0, <= 6.3.2

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

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

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.23 / 6.0.7 or later
Fixed in 4.4.236.0.7
Vendor patch jira.mongodb.org →
Recommended fix High confidence

MongoDB Server 4.4.23+ / 5.0.15+ / 6.0.7+ / 6.3.3+ (depending on current major version)

  1. 1. Identify the currently installed MongoDB Server version using: mongod --version
  2. 2. For MongoDB v4.4.x: Upgrade to MongoDB Server 4.4.23 or later
  3. 3. For MongoDB v5.0.x: Upgrade to MongoDB Server 5.0.15 or later
  4. 4. For MongoDB v6.0.x: Upgrade to MongoDB Server 6.0.7 or later
  5. 5. For MongoDB v6.3.x: Upgrade to MongoDB Server 6.3.3 or later
  6. 6. After upgrade, verify TLS configuration on Windows/macOS specifically: review net.tls.mode, net.tls.certificateKeyFile, net.tls.caFile, and net.tls.allowConnectionsWithoutCertificates settings
  7. 7. Test TLS client certificate validation to confirm proper enforcement
Caveat Minor version upgrades typically low risk but review release notes for any configuration or behavior changes; test in non-production first

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 $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1409 — 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-2023-1409 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