LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23429: Denial of Service (DoS)

All versions of package transpile are vulnerable to Denial of Service (DoS) due to a lack of input sanitization or whitelisting, coupled with improper exception handling in the .to() function.

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-23429 affects the JavaScript package transpile. Untrusted or unexpected input to its .to() function can cause denial of service because input handling and exception handling are insufficient. The direct business risk is application unavailability where this package is used in reachable processing paths.

Executive priority

Treat as a moderate availability issue. Prioritize systems where transpile runs in production request paths or processes external input. Lower priority if limited to offline build tooling, but still track because no fixed version is named in the bundle.

Technical view

The public record describes all versions of transpile as vulnerable to DoS in .to() from missing sanitization or whitelisting and improper exception handling. CVSS 3.1 is 6.5, network reachable, low complexity, no privileges, user interaction required, with high availability impact only.

Likely exposure

Exposure is most likely in JavaScript or Node.js applications that include the transpile package and pass user-influenced values into .to(). The bundle provides no CPEs, no fixed version, and no affected downstream products, so dependency inventory is required.

Exploitation context

The bundle does not report known active exploitation, and KEV is false. CVSS lists exploit code maturity as proof-of-concept, but no exploit details should be assumed beyond the stated DoS condition.

Researcher notes

Evidence is sparse: no CWE, CPE, fixed version, or detailed advisory text is included. The key technical lead is main.js around .to(), with DoS caused by input validation gaps and exception behavior. Avoid assuming impact beyond availability.

Mitigation direction

  • Inventory applications and build tooling for the transpile package.
  • Check Snyk and upstream project guidance for fixed or unaffected versions.
  • Remove or replace transpile if no maintained fix is available.
  • Whitelist expected .to() inputs before calling the function.
  • Add robust exception handling around any remaining .to() usage.
  • Reduce availability impact with rate limits and process supervision.

Validation and detection

  • Review dependency manifests and lockfiles for transpile.
  • Trace whether user-controlled input can reach transpile.to().
  • Confirm deployed versions match the remediated dependency state.
  • Test error handling with benign invalid inputs in a controlled environment.
  • Document whether exposure is runtime-facing or only build-time.
Prepared
Confidence
medium
Sources
4

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-23429 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:N/UI:R/S:U/C:N/I:N/A:H/E:P

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
3Source 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:N/UI:R/S:U/C:N/I:N/A:H/E:P2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H/E:P

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/atranspile0Listed
Weakness

CWE details

No CWE listed

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