LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39187: Crash server with query parameter

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.3, Parse Server crashes when if a query request contains an invalid value for the `explain` option. This is due to a bug in the MongoDB Node.js driver which throws an exception that Parse Server cannot catch. There is a patch for this issue in version 4.10.3. No workarounds aside from upgrading are known to exist.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Parse Server versions before 4.10.3 can crash when handling an invalid query option, causing service disruption. The issue affects availability, not confidentiality or integrity, based on the CVSS vector. Public sources identify version 4.10.3 as the patched release and state no workaround is known besides upgrading.

Executive priority

High priority for organizations using Parse Server, because unauthenticated network traffic can cause downtime in affected versions. The fix path is clear: upgrade. Prioritize systems supporting customer-facing apps or critical business workflows.

Technical view

CVE-2021-39187 is a network-reachable denial-of-service flaw in parse-community Parse Server before 4.10.3. An invalid value for the query `explain` option triggers a MongoDB Node.js driver exception that affected Parse Server versions cannot catch, terminating the server process.

Likely exposure

Exposure is most likely where Parse Server versions earlier than 4.10.3 are deployed and reachable by clients over the network, especially public API backends. The bundle does not identify affected CPEs or downstream packaged products.

Exploitation context

The CVSS vector indicates network access, low attack complexity, no privileges, and no user interaction. CISA KEV is false in the supplied bundle, and no cited source states active exploitation. Treat this as a plausible unauthenticated availability risk, not confirmed exploitation.

Researcher notes

The advisory ties the crash to invalid `explain` option handling and an uncaught MongoDB Node.js driver exception. Sources do not provide evidence of data exposure, code execution, or active exploitation. Keep validation non-destructive and focused on version and exposure checks.

Mitigation direction

  • Upgrade Parse Server to version 4.10.3 or later.
  • Prioritize internet-facing and business-critical Parse Server deployments.
  • Check Parse Server vendor guidance for any newer upgrade recommendations.
  • Monitor affected services for crash loops or abnormal restarts.
  • Review dependency management to prevent reintroducing vulnerable Parse Server versions.

Validation and detection

  • Inventory all Parse Server deployments and record their running versions.
  • Confirm no production or staging instance runs Parse Server below 4.10.3.
  • Review API exposure for Parse Server endpoints reachable from untrusted networks.
  • Check service logs for unexplained crashes around query processing.
  • Run normal application regression tests after upgrading.
Prepared
Confidence
high
Sources
6

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-74: 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
cve · low confidence lookup

CVE-2021-39187 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
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
5Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-39187Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
parse-communityparse-server< 4.10.3Listed
Weakness

CWE details

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

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.