LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23371: Regular Expression Denial of Service (ReDoS)

This affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Applications that use chrono-node to parse user-supplied date text may be slowed or stalled by specially shaped date-like input. The impact is availability, not data theft or code execution. The affected range is chrono-node before 2.2.4.

Executive priority

Treat this as a timely dependency remediation if date parsing is reachable from the internet or high-volume integrations. Business risk is service degradation or outage, not compromise of sensitive data based on the supplied sources.

Technical view

chrono-node before 2.2.4 is affected by Regular Expression Denial of Service. Parsing a date-like string with many embedded spaces can hang due to inefficient regular expression behavior. The CVSS vector indicates network reachability, low attack complexity, no privileges, no user interaction, and high availability impact only.

Likely exposure

Exposure is most likely where chrono-node before 2.2.4 processes untrusted date text from public forms, APIs, search boxes, chat, scheduling, or ingestion pipelines.

Exploitation context

The supplied sources disclose the ReDoS condition and fix reference. CISA KEV is false, and the bundle provides no evidence of active exploitation in the wild.

Researcher notes

Focus review on untrusted input reaching chrono-node parsing before 2.2.4. The public description names embedded-space date-like input as the trigger class. Avoid assuming exploitation or product impact beyond applications that include this package and expose parsing to attacker-controlled text.

Mitigation direction

  • Upgrade chrono-node to version 2.2.4 or later.
  • Check lockfiles for direct and transitive chrono-node dependencies.
  • Limit accepted date input length before parsing.
  • Use request timeouts or worker isolation around untrusted parsing paths.
  • Review vendor advisories for any later guidance.

Validation and detection

  • Inventory package manifests and lockfiles for chrono-node versions below 2.2.4.
  • Use SCA results to find transitive chrono-node exposure.
  • Map application paths where users can submit date-like text.
  • Confirm patched builds no longer depend on vulnerable chrono-node versions.
  • Regression-test date parsing behavior after upgrade.
Prepared
Confidence
high
Sources
5

Public sources used

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.

cve · low confidence lookup

CVE-2021-23371 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
4Source 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-23371Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/achrono-nodeunspecifiedListed
Weakness

CWE details

No CWE listed

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