LiveActive security incident?Get immediate response
CVE Record

CVE-2019-2393: Crash while joining collections with $lookup

A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries, which use $lookup and collations. This issue affects MongoDB Server v4.2 versions prior to 4.2.1; MongoDB Server v4.0 versions prior to 4.0.13 and MongoDB Server v3.6 versions prior to 3.6.15.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-2393 is a MongoDB Server denial-of-service flaw. A user or application account already allowed to run database queries could make affected MongoDB versions crash, disrupting database availability. The sources do not show data theft, data modification, or public active exploitation.

Executive priority

Handle through normal vulnerability management, but prioritize critical databases because exploitation can cause outages. The issue is not described as unauthenticated or actively exploited in the provided sources.

Technical view

The issue affects MongoDB Server 3.6 before 3.6.15, 4.0 before 4.0.13, and 4.2 before 4.2.1. It involves queries using $lookup and collations and is scored CVSS 3.1 6.5 with high availability impact and low privileges required.

Likely exposure

Exposure is most likely where legacy MongoDB Server 3.6, 4.0, or 4.2 deployments remain below the fixed versions and allow application or user accounts to run database queries.

Exploitation context

The CVE requires authenticated query privileges. KEV is false in the provided bundle, and no cited source states active exploitation. Treat this as an availability risk, especially for business-critical MongoDB-backed services.

Researcher notes

The weakness is listed as CWE-416. CVSS indicates network reachability, low attack complexity, low privileges, no user interaction, and availability-only impact. Evidence is limited to the CVE description and MongoDB issue reference.

Mitigation direction

  • Upgrade MongoDB Server to 3.6.15, 4.0.13, 4.2.1, or later applicable versions.
  • Check MongoDB vendor guidance for any deployment-specific remediation details.
  • Review database accounts and remove unnecessary query privileges.
  • Prioritize systems supporting critical applications or exposed to many internal users.

Validation and detection

  • Inventory MongoDB Server versions across production and non-production environments.
  • Confirm no affected deployment is below 3.6.15, 4.0.13, or 4.2.1.
  • Review which users and applications can run database queries.
  • Check operational logs for unexplained MongoDB crashes or availability interruptions.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration 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-2019-2393 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2019-2393Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
MongoDB Inc.MongoDB Server3.6, 4.0, 4.2unaffected
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.