Is CVE-2022-2596 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2022-2596 being exploited in the wild.

How severe is CVE-2022-2596?

Low severity, with a CVSS score of 3.1, published 2 August 2022.

Which products and versions are affected?

node-fetch (npm) SEMVER:introduced=3.0.0,fixed=3.2.10.

Is there a fix for CVE-2022-2596?

Yes. node-fetch (npm): upgrade to 3.2.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2022-2596 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2022-2596?

Check whether you run node-fetch (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2022-2596: node-fetch inefficient regular expression complexity

CVE-2022-2596 · Severity: low · CVSS 3.1 · Published 2022-08-02

node-fetch is a lightweight module that brings the Fetch API to Node.js applications, commonly used for HTTP requests. A flaw in how it validates URL trustworthiness allows attackers to send specially crafted URLs that cause excessive processing delays, potentially degrading application performance or causing denial of service.

Technologies: node-fetch (npm). Vendors: npm.

Quick answers

Is CVE-2022-2596 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2022-2596 being exploited in the wild.
How severe is CVE-2022-2596?: Low severity, with a CVSS score of 3.1, published 2 August 2022.
Which products and versions are affected?: node-fetch (npm) SEMVER:introduced=3.0.0,fixed=3.2.10.
Is there a fix for CVE-2022-2596?: Yes. node-fetch (npm): upgrade to 3.2.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2022-2596 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2022-2596?: Check whether you run node-fetch (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

node-fetch (npm): upgrade to 3.2.10 or later
```
npm install node-fetch@3.2.10
```

Technical details

This is a Regular Expression Denial of Service (ReDoS) vulnerability in the isOriginPotentiallyTrustworthy() function within referrer.js. The vulnerable regex pattern has catastrophic backtracking behavior when processing malformed URLs with alternating letters and periods (e.g., 'http://a.a.a.a...a'). The vulnerability is network-accessible and requires no authentication or user interaction—an attacker can trigger it by passing a crafted URL to the fetch function. Exploitation can cause CPU exhaustion and response delays; a 76-character payload demonstrated 42+ second execution times. The vulnerability affects versions 3.0.0 through 3.2.9 and is fixed in version 3.2.10.

Affected products

node-fetch node-fetch 3.0.0 through 3.2.9

Identifiers

CVE-2022-2596
GHSA-vp56-6g26-6827

Timeline

2022-08-02: disclosed
2022-07-31: patched: Fixed in version 3.2.10

References

https://github.com/node-fetch/node-fetch/pull/1611

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.