MediumPublic exploit

ReDoS in parse-uri v1.0.9

IdentifiersCVE-2024-36751CWE-1333· Inefficient Regular Expression…

CVE-2024-36751 is a Regular Expression Denial of Service (ReDoS) vulnerability in the npm package parse-uri version 1.0.9. The issue is triggered when the library parses a crafted URL that causes excessive regular-expression backtracking. The available context indicates the vulnerable behavior occurs during URL parsing in the package, but does not identify the exact vulnerable function or regex implementation. A reported working exploit example uses the parse-uri package with a crafted URL containing approximately 30,000 repeated 'a' characters to trigger pathological regex processing and stall execution.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can drive excessive CPU consumption and event-loop blockage in Node.js applications that parse attacker-controlled URLs with the affected package. This can degrade performance or render the service unavailable, resulting in denial of service. No evidence in the provided content indicates confidentiality, integrity, or code-execution impact.

Mitigation

If you can’t patch tonight, do this now.

Do not pass untrusted or attacker-controlled URLs to the affected library until remediation is in place. Enforce strict input length and complexity limits on URLs before parsing, especially on path and query components. Apply request timeouts, CPU/resource limits, and rate limiting to reduce the likelihood of sustained CPU exhaustion. Where feasible, replace parse-uri with an alternative parser that does not rely on vulnerable regex patterns.

Remediation

Patch, then assume compromise.

Upgrade to a fixed, non-vulnerable version if one is available. The provided content identifies parse-uri v1.0.9 as affected but does not specify a fixed release. If no vendor fix is available, patch or replace the dependency by removing or rewriting the vulnerable regular expression to eliminate catastrophic backtracking, or migrate to a maintained alternative URL parsing library.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

AnyParse-Uriapplication

AnyParseuriapplication

npm, Inc.Parse-Uriapplication

npm, Inc.Parseuriapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

1 SOURCESView more in app

arxivNews

Jul 18, 2024

PoCGen: Generating Proof-of-Concept Exploits for Vulnerabilities in Npm Packages

A ReDoS vulnerability in the parse-uri package (v1.0.9) that can be triggered via a crafted URL, highlighted as an example of a real-world vulnerability lacking a PoC exploit in its report.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity