CVE-2023-32005

MEDIUM

5.3

CVSS Score

Published: September 12, 2023 at 01:36 AM UTC

Updated: June 17, 2026 at 05:57 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

Start Free Sign In

Severity

MEDIUM5.3

Exploit prediction

EPSS 1%

SSVC

PoC

Description

A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument. This flaw arises from an inadequate permission model that fails to restrict file stats through the `fs.statfs` 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. 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.

Node.js · Node.js

95%

10.0 ≤ v < 10.*11.0 ≤ v < 11.*12.0 ≤ v < 12.*13.0 ≤ v < 13.*14.0 ≤ v < 14.*15.0 ≤ v < 15.*17.0 ≤ v < 17.*19.0 ≤ v < 19.*20.0 ≤ v < 20.5.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.0 11.0 12.0 13.0 14.0 15.0 17.0 19.0 20.0 4.0 5.0 6.0 7.0 8.0 9.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 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.5.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.

References (2)

ExploitThird Party Advisory

Source: [email protected]

https://hackerone.com/reports/2051224

Third Party AdvisoryVDB Entry

Source: [email protected]

https://security.netapp.com/advisory/ntap-20231103-0004/

SSVC — Action Prioritization

SSVCPoCAutomatablePartial impact

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

CVSS

5.3MEDIUMCISA-ADP

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: LOW
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-732

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.

Create account Sign in

Free plan, no card