Incomplete Documentation Affecting nodejs:20/nodejs-packaging package, versions <0:2021.06-4.module+el9.3.0+19518+63aad52d


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.05% (18th 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 IDSNYK-RHEL9-NODEJS-7879051
  • published3 Sept 2024
  • disclosed19 Feb 2024

Introduced: 19 Feb 2024

CVE-2024-21890  (opens in a new tab)
CWE-1059  (opens in a new tab)

How to fix?

Upgrade RHEL:9 nodejs:20/nodejs-packaging to version 0:2021.06-4.module+el9.3.0+19518+63aad52d or higher.
This issue was patched in RHSA-2024:1688.

NVD Description

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

The Node.js Permission Model does not clarify in the documentation that wildcards should be only used as the last character of a file path. For example:

 --allow-fs-read=/home/node/.ssh/*.pub

will ignore pub and give access to everything after .ssh/.

This misleading documentation affects all users using the experimental permission model in Node.js 20 and Node.js 21.

Please note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.

CVSS Scores

version 3.1