First published: Thu Aug 10 2023(Updated: )
The use of the deprecated API process.binding() can bypass the policy mechanism by requiring internal modules and eventually take advantage of process.binding('spawn_sync') run arbitrary code, outside of the limits defined in a policy.json file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Security Advisory: <a href="https://nodejs.org/en/blog/vulnerability/august-2023-security-releases#permissions-policies-can-be-bypassed-via-processbinding-mediumcve-2023-32559">https://nodejs.org/en/blog/vulnerability/august-2023-security-releases#permissions-policies-can-be-bypassed-via-processbinding-mediumcve-2023-32559</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Node.js | >=16.0.0<21.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2230956 is marked as medium due to the potential for policy bypass using deprecated APIs.
To fix REDHAT-BUG-2230956, upgrade to a Node.js version that is outside the vulnerable range of 16.0.0 to 21.0.0.
REDHAT-BUG-2230956 affects Node.js versions between 16.0.0 and 21.0.0 that utilize the deprecated API process.binding().
The impact of REDHAT-BUG-2230956 is the potential execution of arbitrary code, circumventing the defined security policies.
Yes, REDHAT-BUG-2230956 specifically involves internal modules accessed through the process.binding() method.