Rapid7 Vulnerability & Exploit Database

Red Hat: CVE-2021-43616: CVE-2021-43616 npm: npm ci succeeds when package-lock.json doesn't match package.json (Multiple Advisories)

Free InsightVM Trial No Credit Card Necessary
Watch Demo See how it all works
Back to Search

Red Hat: CVE-2021-43616: CVE-2021-43616 npm: npm ci succeeds when package-lock.json doesn't match package.json (Multiple Advisories)

Severity
8
CVSS
(AV:N/AC:L/Au:N/C:P/I:P/A:P)
Published
11/13/2021
Created
06/01/2022
Added
05/31/2022
Modified
12/15/2023

Description

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.

Solution(s)

  • redhat-upgrade-nodejs
  • redhat-upgrade-nodejs-debuginfo
  • redhat-upgrade-nodejs-debugsource
  • redhat-upgrade-nodejs-devel
  • redhat-upgrade-nodejs-docs
  • redhat-upgrade-nodejs-full-i18n
  • redhat-upgrade-nodejs-nodemon
  • redhat-upgrade-nodejs-packaging
  • redhat-upgrade-npm

With Rapid7 live dashboards, I have a clear view of all the assets on my network, which ones can be exploited, and what I need to do in order to reduce the risk in my environment in real-time. No other tool gives us that kind of value and insight.

– Scott Cheney, Manager of Information Security, Sierra View Medical Center

;