dbcve.org
C\+\+Application · MongoDB

CVE-2021-32050

HIGH · 7.5 CVSS v3.1 Published 2023-08-29
Fix available
A fix is available. Upgrade to 1.1.1 / 1.9.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

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
Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed. Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default). This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).

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
How this class of weakness works · CWE-200

The application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.

General guidance for the information exposure class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
C\+\+Application
Affected:>= 1.0.0, < 1.17.7
C DriverApplication
Affected:>= 1.0.0, < 1.17.7
Node.jsApplication
Affected:>= 3.6, < 3.6.10>= 4.0, < 4.17.0>= 5.0, < 5.8.0
Php DriverApplication
Affected:>= 1.0.0, < 1.9.2
Swift DriverApplication
Affected:>= 1.0.0, < 1.1.1

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

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

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 1.1.1 / 1.9.2 / 1.17.7 or later
Fixed in 1.1.11.9.21.17.7
Vendor patch jira.mongodb.org →
Recommended fix High confidence

Upgrade to C Driver 1.17.7, C++ Driver 3.7.0+, PHP Driver 1.9.2+, Swift Driver 1.1.1+, or Node.js Driver 3.6.10+/4.17.0+/5.8.0+ depending on your driver

  1. Identify which MongoDB driver(s) your application uses (C++, C, Node.js, PHP, or Swift)
  2. Check your current driver version using your package manager or dependency manifest
  3. For Node.js driver: upgrade to 3.6.10 (if using 3.x), 4.17.0 (if using 4.x), or 5.8.0 (if using 5.x)
  4. For PHP driver: upgrade to 1.9.2 or later
  5. For Swift driver: upgrade to 1.1.1 or later
  6. For C driver: upgrade to 1.17.7 or later
  7. For C++ driver: upgrade to 3.7.0 or later (which includes the fixed C driver 1.17.7)
  8. Update your package.json, composer.json, Podfile, or equivalent dependency file with the new version
Caveat Minor: Node.js driver 4.x and 5.x may have breaking changes unrelated to this fix; review the driver's changelog for your version upgrade path

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,250. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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