CVE-2024-22020VulnerabilityPublished 3 Sep 2024Updated 13 Oct 2026

Red Hat Security Advisory: nodejs:18 security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2024-28863

Not known to be exploited : upgrade to 18.20.5 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.20.5

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Red Hat to 18.20.5.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=18.20.4 <18.20.5 Red Hat Red Hat Enterprise Linux Red Hat Enterprise Linux AppStream (v. 9) src nodejs-1:18.20.4-1.module+el9.4.0+22195+c221878e.src::nodejs:18	Fixed in 18.20.5

AI-suggested

Red Hat has released an official security update for Node.js 18 on Red Hat Enterprise Linux 9 and related variants that addresses these vulnerabilities. Users should apply the update as described in Red Hat advisory RHSA-2024:6147 and the linked article https://access.redhat.com/articles/11258. No additional mitigation steps are indicated beyond applying the official patch.

Description

A security update for Node.js addresses two vulnerabilities: a denial of service in node-tar due to lack of folder depth validation (CVE-2024-28863) and a bypass of network import restrictions via data URL in Node.js (CVE-2024-22020). The update is rated as moderate severity by Red Hat Product Security and affects Node.js 18 on Red Hat Enterprise Linux 9 and related distributions. The update mitigates these issues by applying patches provided by Red Hat.

Impact

The denial of service vulnerability (CVE-2024-28863) could allow an attacker to cause resource exhaustion by exploiting the lack of folder depth validation in tar file parsing. The network import restriction bypass (CVE-2024-22020) could allow an attacker to circumvent security controls intended to restrict network imports, potentially leading to unauthorized code execution or data access. Red Hat rates the overall impact as moderate.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:32 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats