VYPR
Unrated severityNVD Advisory· Published Jul 19, 2019· Updated Aug 6, 2024

Authentication bypass when using LDAP authentication in MongoDB Enterprise Server

CVE-2015-7882

Description

MongoDB Enterprise 3.0.0-3.0.6 improperly handles LDAP authentication, allowing unauthenticated access.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

MongoDB Enterprise 3.0.0-3.0.6 improperly handles LDAP authentication, allowing unauthenticated access.

Vulnerability

MongoDB Enterprise versions 3.0.0 through 3.0.6 (inclusive) improperly handle LDAP authentication [1]. When LDAP is enabled, the authentication mechanism "PLAIN" is exposed, allowing bypass. Only Enterprise edition is affected; Community edition is not.

Exploitation

An unauthenticated attacker can gain unauthorized access to a MongoDB instance or cluster by exploiting the LDAP authentication flaw. No authentication is required; the attacker simply needs network access to the MongoDB port. The vulnerability exists because the "PLAIN" mechanism is enabled, which can be checked via the db.adminCommand({getParameter: 1, authenticationMechanisms: 1}) command [1].

Impact

Successful exploitation allows an attacker to gain unauthorized access to the MongoDB instance or cluster, bypassing authentication. This leads to potential data disclosure, modification, or deletion, depending on the privileges of the accessed user [1].

Mitigation

Upgrade to MongoDB Enterprise 3.0.7, which includes the fix [1]. No workarounds are available. Affected users should upgrade as soon as possible. The Community edition is not vulnerable.

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2
  • MongoDB/Serverdescription
  • MongoDB/Serverllm-fuzzy
    Range: >= 3.0.0, <= 3.0.6

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.