LiveActive security incident?Get immediate response
CVE Record

CVE-2015-7882: Authentication bypass when using LDAP authentication in MongoDB Enterprise Server

Improper handling of LDAP authentication in MongoDB Server versions 3.0.0 to 3.0.6 allows an unauthenticated client to gain unauthorized access.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

MongoDB Enterprise Server 3.0.0 through 3.0.6 had an LDAP authentication bypass. In affected deployments, an unauthenticated network client could gain unauthorized access, creating confidentiality, integrity, and availability risk for stored data and dependent services.

Executive priority

Treat this as a high-priority legacy exposure issue. It affects old MongoDB Enterprise deployments, but the potential business impact is severe because authentication bypass can expose or alter database contents.

Technical view

The CVE describes improper LDAP authentication handling in MongoDB Server versions 3.0.0 to 3.0.6. CVSS 3.0 is 8.1: network reachable, no privileges or user interaction required, high impact to confidentiality, integrity, and availability, but high attack complexity.

Likely exposure

Exposure is most likely in legacy MongoDB Enterprise deployments running versions 3.0.0 through 3.0.6 with LDAP authentication enabled. The source bundle does not identify other affected products or CPEs.

Exploitation context

The CVE source says unauthenticated clients can gain unauthorized access. CISA KEV is false in the supplied bundle, and no cited source states active exploitation or public exploit availability.

Researcher notes

Evidence is limited to the CVE description and MongoDB JIRA reference. The affected range is clear, but the supplied bundle does not include detailed root cause, exploit conditions beyond LDAP handling, or a named fixed release.

Mitigation direction

  • Identify any MongoDB Enterprise 3.0.0 through 3.0.6 instances using LDAP authentication.
  • Check MongoDB guidance for SERVER-20691 before selecting the target fixed version.
  • Prioritize migration away from affected releases where LDAP authentication is in use.
  • Restrict network access to exposed MongoDB services while remediation is planned.
  • Review authentication logs for unexpected LDAP-authenticated or unauthenticated access patterns.

Validation and detection

  • Inventory MongoDB versions across production, staging, and backup environments.
  • Confirm whether LDAP authentication is configured on each MongoDB Enterprise instance.
  • Verify affected instances are no longer running versions 3.0.0 through 3.0.6.
  • Check access logs for anomalous successful authentications around exposed services.
  • Document compensating controls if immediate remediation is not possible.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2015-7882 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.1High
CVSS 3.0 vector shape for CVE-2015-7882Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.