Insufficient Verification of Data Authenticity Affecting nodejs-packaging package, versions <0:25-1.module+el8.5.0+702+221f14e6


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
2.46% (91st 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-ROCKY8-NODEJSPACKAGING-3198865
  • published5 Jan 2023
  • disclosed13 Nov 2021

Introduced: 13 Nov 2021

CVE-2021-43616  (opens in a new tab)
CWE-345  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:8 nodejs-packaging to version 0:25-1.module+el8.5.0+702+221f14e6 or higher.
This issue was patched in RLSA-2022:4796.

NVD Description

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

The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.

CVSS Scores

version 3.1