Overview
Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. It offers an event-driven, non-blocking I/O model that makes it lightweight and efficient, and is widely used in server-side applications.
An privilege escalation vulnerability has been identified in Node.js. The issue stems from the use of the deprecated API process.binding() which can bypass the policy mechanism. This weakness allows attackers to execute arbitrary code outside of the limits defined in a policy.json file.
This vulnerability affects specific versions of the package and can result in unauthorized access. Details on affected versions and reproduction steps are provided below.
Details
Module Info
Affected packages: Node.js
Affected versions: 4 <= 16.20.1, 0 <= 18.17.0, 0 <= 20.5.0
GitHub repository: https://github.com/nodejs/node
Published packages: https://github.com/nodejs/node/releases
Package manager: npm
Fixed in: Node.js NES version 14.
Vulnerability Info
The issue stems from the use of the deprecated API process.binding().
For instance, in Node.js, if the deprecated API is used, the system can execute arbitrary code. This behavior can be exploited by attackers to gain unauthorized access.
This vulnerability is a result of flawed logic, and may allow attackers to execute arbitrary code.
- https://www.cve.org/CVERecord?id=CVE-2023-32559
- https://hackerone.com/reports/1946470
Credits
- Leodog896
Mitigation
This vulnerability is not fixed upstream due to the release line being EOL. HeroDevs has issued patched builds under the NES (Never Ending Support) line.
- Update to a patched LTS version of Node.js
- Leverage a commercial support partner like HeroDevs for post-EOL security.
Refer to the NES documentation for upgrade instructions.
