CVE-2023-32005
First published: Tue Sep 12 2023(Updated: )
Node.js could allow a remote attacker to obtain sensitive information, caused by the failure to restrict file stats through the fs.statfs API in the permission model. By using the --allow-fs-read flag with a non-* argument, an attacker could exploit this vulnerability to retrieve stats from files that they do not have explicit read access to.
Credit: support@hackerone.com support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Nodejs Node.js | >=20.0.0<20.5.1 | |
| Nodejs Node.js | >=20.0.0<=20.6.1 | |
| <=2.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID?
The vulnerability ID is CVE-2023-32005.
Which version of Node.js is affected by this vulnerability?
Node.js version 20 is affected.
What is the severity level of CVE-2023-32005?
The severity level of CVE-2023-32005 is medium with a score of 5.3.
How does this vulnerability affect Node.js users?
This vulnerability affects users of the experimental permission model when the --allow-fs-read flag is used with a non-* argument.
How can I fix the vulnerability in Node.js version 20?
To fix the vulnerability in Node.js version 20, you should update to a version higher than 20.6.1.
- collector/nvd-index
- collector/nvd-api
- agent/references
- agent/author
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- agent/event
- collector/ibm-support
- source/IBM
- agent/software-canonical-lookup
- agent/weakness
- agent/severity
- agent/description
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- vendor/nodejs
- canonical/nodejs node.js
- version/nodejs node.js/20.0.0
- version/nodejs node.js/20.6.1
- vendor/ibm
- canonical/ibm planning analytics
- version/ibm planning analytics/2.0