CVE-2024-22018

LOW
2.9
CVSS Score
Published: July 10, 2024 at 01:00 AM UTC
Updated: June 17, 2026 at 07:10 AM UTC
1 product affected across 1 vendorNode.js

Using Node by NodeJS?

Get instant alerts when new vulnerabilities affect Node - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.9
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

A vulnerability has been identified in Node.js, affecting users of the experimental permission model when the --allow-fs-read flag is used. This flaw arises from an inadequate permission model that fails to restrict file stats through the fs.lstat API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to. This vulnerability affects all users using the experimental permission model in Node.js 20 and Node.js 21. Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0 ≤ v < 10.*11.0 ≤ v < 11.*12.0 ≤ v < 12.*13.0 ≤ v < 13.*14.0 ≤ v < 14.*15.0 ≤ v < 15.*16.0 ≤ v < 16.*17.0 ≤ v < 17.*19.0 ≤ v < 19.*20.0 ≤ v < 20.15.121.0 ≤ v < 21.*22.0 ≤ v < 22.4.14.0 ≤ v < 4.*5.0 ≤ v < 5.*6.0 ≤ v < 6.*7.0 ≤ v < 7.*8.0 ≤ v < 8.*9.0 ≤ v < 9.*10.011.012.013.014.015.016.017.019.020.021.022.04.05.06.07.08.09.0
Affected range stops below 10.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 11.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 12.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 14.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.15.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.*, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2.9LOWhackerone
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card