Arbitrary Code Injection Affecting nodejs:18/nodejs package, versions <1:18.17.1-1.module+el9.2.0.z+19753+58118bc0


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.08% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL9-NODEJS-5848172
  • published22 Aug 2023
  • disclosed9 Aug 2023

Introduced: 9 Aug 2023

CVE-2023-32559  (opens in a new tab)
CWE-94  (opens in a new tab)

How to fix?

Upgrade RHEL:9 nodejs:18/nodejs to version 1:18.17.1-1.module+el9.2.0.z+19753+58118bc0 or higher.
This issue was patched in RHSA-2023:5363.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:18/nodejs package and not the nodejs:18/nodejs package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API process.binding() can bypass the policy mechanism by requiring internal modules and eventually take advantage of process.binding(&#39;spawn_sync&#39;) 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.

CVSS Scores

version 3.1