dbcve.org
MongoDBDatabase / datastore

CVE-2018-20804

MEDIUM · 6.5 CVSS v3.1 Published 2020-11-23
Fix available
A fix is available. Upgrade to 3.6.13 / 4.0.10 or later.
See remediation →
71/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
A user authorized to perform database queries may trigger denial of service by issuing specially crafted applyOps invocations. This issue affects MongoDB Server v4.0 versions prior to 4.0.10 and MongoDB Server v3.6 versions prior to 3.6.13.

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

An authenticated MongoDB user with database query permissions can trigger denial of service by issuing specially crafted applyOps commands, causing the server to crash or become unresponsive.

MitigationUpgrade MongoDB Server to v4.0.10 or later for 4.0.x versions, or v3.6.13 or later for 3.6.x versions.

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:>= 3.6.0, < 3.6.13>= 4.0.0, < 4.0.10

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine installed MongoDB version
    Run 'db.version()' in the mongo shell or execute 'mongod --version' from command line
    Affected if Version is 3.6.0 through 3.6.12, or 4.0.0 through 4.0.9 (falls within <3.6.13 or <4.0.10)
  2. Verify MongoDB is running with authentication enabled
    Check the configuration file (default /etc/mongod.conf) for 'security: authorization: enabled' or run 'db.adminCommand({getParameter: 1, authEnabled: 1})' in the mongo shell
    Affected if Authentication is disabled (authorization set to 'disabled' or not set)
  3. Confirm database user accounts exist
    Run 'use admin; db.system.users.find()' in the mongo shell to list all users
    Affected if Any authenticated users exist with read or readWrite roles on any database (they can issue query commands)
  4. Check for user query permissions
    Run 'use admin; db.system.users.find().forEach(function(u){ print(u.user + ': ' + JSON.stringify(u.roles)); })' to list user roles
    Affected if Any user has roles containing 'read' or 'readWrite' on any database, granting query permissions needed to trigger applyOps

Your environment is affected if MongoDB is version 3.6.0-3.6.12 or 4.0.0-4.0.9 AND has authentication enabled with at least one user who has query permissions on any database.

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.

From vendor data
Upgrade available Upgrade to 3.6.13 / 4.0.10 or later
Fixed in 3.6.134.0.10
Interim mitigation

Upgrade MongoDB Server to v4.0.10 or later for 4.0.x versions, or v3.6.13 or later for 3.6.x versions.

Fix this in MongoDB Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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