dbcve.org
MongoDBDatabase / datastore

CVE-2024-6384

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 6.0.16 / 7.0.11 or later.
See remediation →
59/100
Remediation priority · Elevated
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
"Hot" backup files may be downloaded by underprivileged users, if they are capable of acquiring a unique backup identifier. This issue affects MongoDB Enterprise Server v6.0 versions prior to 6.0.16, MongoDB Enterprise Server v7.0 versions prior to 7.0.11 and MongoDB Enterprise Server v7.3 versions prior to 7.3.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 confidence

MongoDB Enterprise Server contains an improper access control vulnerability in its backup download mechanism. Underprivileged users who obtain a unique backup identifier can directly download 'hot' backup files without proper authorization verification, bypassing intended access controls.

MitigationUpgrade MongoDB Enterprise Server to v6.0.16, v7.0.11, or v7.3.3 or later to receive the patch that adds proper authorization checks for backup file downloads.

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:>= 6.0.0, < 6.0.16>= 7.0.0, < 7.0.11>= 7.3.0, < 7.3.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Confirm MongoDB Enterprise Edition is installed
    Run 'db.version()' in mongosh and check the build info via 'db.adminCommand({buildInfo:1})' - look for 'modules' field containing 'enterprise' or check the binary name (mongod vs mongod-enterprise)
    Affected if The installation is MongoDB Enterprise Server rather than Community Edition (only Enterprise is affected)
  2. Determine the installed MongoDB version
    Run 'db.adminCommand({buildInfo:1})' in mongosh and examine the 'version' field (for example, '7.0.5')
    Affected if The version falls within: 6.0.0 to 6.0.15, 7.0.0 to 7.0.10, or 7.3.0 to 7.3.2
  3. Verify if backup functionality is configured
    Check for presence of backup-related configuration: query the 'admin' database for 'backup' settings, or inspect mongod.conf for backup configuration sections, or check for 'backup' role assignments via 'db.adminCommand({rolesInfo:1})'
    Affected if Backup functionality is enabled or configured in the environment
  4. Review audit logs for backup download events
    If audit logging is enabled, search audit logs for events with 'backup' in the operation type or 'download' action. Check the audit destination (file or syslog) configured in mongod.conf
    Affected if Audit logs show backup download operations by users without the required backup roles

You are affected if running MongoDB Enterprise Server version 6.0.0-6.0.15, 7.0.0-7.0.10, or 7.3.0-7.3.2 with backups configured and no additional access controls on backup downloads.

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 6.0.16 / 7.0.11 / 7.3.3 or later
Fixed in 6.0.167.0.117.3.3
Interim mitigation

Upgrade MongoDB Enterprise Server to v6.0.16, v7.0.11, or v7.3.3 or later to receive the patch that adds proper authorization checks for backup file downloads.

Recommended fix High confidence

Upgrade to MongoDB 6.0.16+, 7.0.11+, or 7.3.3+ (choose the major version branch matching your current deployment)

  1. 1. Ensure you have a complete backup of your MongoDB data before proceeding with any upgrade.
  2. 2. Review MongoDB's upgrade documentation for your specific version path (e.g., upgrading from 6.0.x to 6.0.16).
  3. 3. For MongoDB Enterprise installations, use your package manager or manual tarball extraction to upgrade to the target version.
  4. 4. For MongoDB Community Edition, obtain the corresponding fixed version from MongoDB's official downloads.
  5. 5. After upgrading, verify that the MongoDB service starts successfully and all data is accessible.
  6. 6. Test that the authorization controls properly restrict access to backup files.
Caveat Standard MongoDB upgrade considerations apply - review release notes for deprecation warnings and ensure application compatibility with the target minor version

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

Fix this in MongoDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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