MongoDBDatabase / datastore
CVE-2024-8654
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 Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are called in internal aggregation stage. This issue affected MongoDB Server v6.0 version 6.0.3.
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 confidenceA memory safety vulnerability in MongoDB Server v6.0.3 allows access to non-initialized memory regions when zero arguments are passed to an internal aggregation stage, potentially leading to information disclosure, denial of service, or arbitrary code execution.
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
>= 6.0.0, <= 6.0.3CVSS 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
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 installed MongoDB Server versionRun 'db.version()' in mongosh/mongo shell, or execute 'mongod --version' from command lineAffected if Version is 6.0.0, 6.0.1, 6.0.2, or 6.0.3 (falls within >= 6.0.0, <= 6.0.3)
-
Identify aggregation pipeline usageReview application code and MongoDB logs for any use of $bucket, $collStats, $facet, $geoNear, $graphLookup, $group, $indexStats, $limit, $lookup, $match, $merge, $out, $project, $redact, $sample, $set, $skip, $sort, $sortByCount, $unset, or $unwind stages with empty argument arraysAffected if Any internal aggregation stage is called with zero arguments or an empty array
-
Audit stored aggregation definitionsCheck any stored procedures, views, or materialized views that define aggregation pipelines, using 'db.getCollectionInfos()' and reviewing 'pipeline' fieldsAffected if Stored pipelines contain aggregation stages invoked without arguments
You are affected if your MongoDB Server version is 6.0.0 through 6.0.3 AND you have aggregation pipelines using internal stages with zero arguments.
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 · scopedUpgrade MongoDB Server from version 6.0.3 to version 6.0.4 or later to patch the memory access vulnerability. Schedule a maintenance window and ensure backups are in place before performing the upgrade.
MongoDB Server 6.0.4 or later
- Download MongoDB Server version 6.0.4 or later from the official MongoDB downloads page (https://www.mongodb.com/try/download/community)
- Ensure all MongoDB services are stopped before upgrading
- Back up all database data and configuration files
- Install the new version of MongoDB Server
- Verify the upgrade by starting the MongoDB service
- Run the db.adminCommand({getLog: 'startupWarnings'}) command to check for any post-upgrade warnings
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8654 — 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-2024-8654 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