dbcve.org
MongoDBDatabase / datastore

CVE-2024-10921

HIGH · 8.1 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 5.0.30 / 6.0.19 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
An authorized user may trigger crashes or receive the contents of buffer over-reads of Server memory by issuing specially crafted requests that construct malformed BSON in the MongoDB Server. This issue affects MongoDB Server v5.0 versions prior to 5.0.30 , MongoDB Server v6.0 versions prior to 6.0.19, MongoDB Server v7.0 versions prior to 7.0.15 and MongoDB Server v8.0 versions prior to and including 8.0.2.

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

A BSON parsing vulnerability in MongoDB Server allows authorized users to trigger denial-of-service crashes or achieve information disclosure through buffer over-reads by sending specially crafted requests with malformed BSON data. This affects multiple major versions from 5.0 through 8.0.

MitigationUpgrade MongoDB Server to version 5.0.30+, 6.0.19+, 7.0.15+, or 8.0.3+ to patch the BSON parsing vulnerability. Since this requires authenticated access, also review user permissions and implement least-privilege access controls.

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.30>= 6.0.0, < 6.0.19>= 7.0.0, < 7.0.15>= 8.0.0, < 8.0.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 MongoDB Server version
    Run 'db.version()' in the mongo shell or use 'mongod --version' from command line to obtain the exact installed version string
    Affected if The version falls within 5.0.0-5.0.29, 6.0.0-6.0.18, 7.0.0-7.0.14, or 8.0.0-8.0.2
  2. Confirm MongoDB service is running
    Check process status with 'ps aux | grep mongod' or verify the service is listening on the configured port (default 27017) using 'netstat -tlnp | grep 27017'
    Affected if The MongoDB service is active and accessible on the network
  3. Verify authentication is enabled
    Check the configuration file (typically /etc/mongod.conf) for 'security.authorization' setting or run 'db.getSiblingDB("admin").system.version.findOne({_id:"authSchemaVersion"})' in the mongo shell
    Affected if Authentication is disabled OR authenticated users with any database access exist (since the vulnerability requires authenticated access to trigger)
  4. Identify active database users and their roles
    Run 'db.getSiblingDB("admin").system.users.find({}, {user:1, db:1, roles:1})' in the mongo shell to list all users and their assigned roles
    Affected if Any authenticated users exist with permissions to send queries to any database, as the vulnerability can be triggered by sending malformed BSON in regular database operations

You are affected if your MongoDB Server version is 5.0.0-5.0.29, 6.0.0-6.0.18, 7.0.0-7.0.14, or 8.0.0-8.0.2 AND the server is running with authenticated users able to send queries.

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.30 / 6.0.19 / 7.0.15 or later
Fixed in 5.0.306.0.197.0.15
Interim mitigation

Upgrade MongoDB Server to version 5.0.30+, 6.0.19+, 7.0.15+, or 8.0.3+ to patch the BSON parsing vulnerability. Since this requires authenticated access, also review user permissions and implement least-privilege access controls.

Recommended fix High confidence

5.0.30 (for 5.0.x), 6.0.19 (for 6.0.x), 7.0.15 (for 7.0.x), or 8.0.3 (for 8.0.x)

  1. Identify the currently installed MongoDB version using: db.version() or mongod --version
  2. Determine which major version line you are on (5.0, 6.0, 7.0, or 8.0)
  3. For MongoDB 5.0.x: Upgrade to version 5.0.30 or later
  4. For MongoDB 6.0.x: Upgrade to version 6.0.19 or later
  5. For MongoDB 7.0.x: Upgrade to version 7.0.15 or later
  6. For MongoDB 8.0.x: Upgrade to version 8.0.3 or later
  7. Review MongoDB upgrade documentation for your deployment type (standalone, replica set, or sharded cluster)
  8. Create a full backup of all databases before initiating the upgrade
Caveat Review release notes for any behavior changes between versions; test application compatibility in staging before production upgrade

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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