dbcve.org
MongoDBDatabase / datastore

CVE-2024-3372

HIGH · 7.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 5.0.25 / 6.0.14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Improper validation of certain metadata input may result in the server not correctly serialising BSON. This can be performed pre-authentication and may cause unexpected application behavior including unavailability of serverStatus responses. This issue affects MongoDB Server v7.0 versions prior to 7.0.6, MongoDB Server v6.0 versions prior to 6.0.14 and MongoDB Server v.5.0 versions prior to 5.0.25.

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 confidence

MongoDB Server has improper validation of certain metadata input that causes incorrect BSON serialization. This vulnerability is exploitable pre-authentication and can cause unexpected behavior including unavailability of serverStatus responses, resulting in a denial-of-service condition.

MitigationUpgrade MongoDB Server to version 7.0.6+, 6.0.14+, or 5.0.25+ respectively to apply the vendor patch.

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
MongoDBDatabase / datastore
Affected:>= 5.0.0, < 5.0.25>= 6.0.0, < 6.0.14>= 7.0.0, < 7.0.6

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

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MongoDB version
    Run 'db.version()' in mongosh/mongo shell, or execute 'mongod --version' from command line, or check package manager
    Affected if Version falls within 5.0.0-5.0.24, 6.0.0-6.0.13, or 7.0.0-7.0.5
  2. Verify MongoDB server is network accessible
    Attempt connection to MongoDB port (default 27017) via telnet, nc, or application connection
    Affected if Instance is reachable over network and version is in affected range
  3. Test serverStatus command availability
    Run 'db.serverStatus()' in mongosh and observe if command completes or hangs
    Affected if Command fails, times out, or returns error due to BSON serialization issues
  4. Check for unexpected server behavior
    Monitor MongoDB logs for errors related to BSON serialization, metadata validation, or serverStatus failures
    Affected if Logs show serialization errors or serverStatus endpoint issues with version in affected range

User is affected if MongoDB server version is 5.0.0-5.0.24, 6.0.0-6.0.13, or 7.0.0-7.0.5 and exhibits serverStatus failures or BSON-related errors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 5.0.25 / 6.0.14 / 7.0.6 or later
Fixed in 5.0.256.0.147.0.6
Interim mitigation

Upgrade MongoDB Server to version 7.0.6+, 6.0.14+, or 5.0.25+ respectively to apply the vendor patch.

Recommended fix High confidence

MongoDB 5.0.25 / 6.0.14 / 7.0.6 (depending on current branch)

  1. Identify the currently installed MongoDB version using db.version() or mongod --version
  2. Determine which release branch (5.0.x, 6.0.x, or 7.0.x) your current version belongs to
  3. For 5.0.x branch: Upgrade to MongoDB 5.0.25 or later
  4. For 6.0.x branch: Upgrade to MongoDB 6.0.14 or later
  5. For 7.0.x branch: Upgrade to MongoDB 7.0.6 or later
  6. Follow standard MongoDB upgrade procedures for your deployment type (standalone, replica set, or sharded cluster)
  7. After upgrade, verify serverStatus command returns normally to confirm the fix is effective
Caveat Review MongoDB release notes for any compatibility changes between your current version and target fixed version before upgrading

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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