CVE-2021-43616

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.
ProviderTypeBase ScoreAtk. VectorAtk. ComplexityPriv. RequiredVector
NISTNIST
9 CRITICAL
NETWORK
HIGH
NONE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
mitreCNA
9 CRITICAL
NETWORK
HIGH
NONE
CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N
CVEADP
---
---
Base Score
CVSS 3.x
EPSS Score
Percentile: 72%
VendorProductVersion
npmjsnpm
7.0.0 ≤
𝑥
≤ 7.24.2
npmjsnpm
8.0.0 ≤
𝑥
≤ 8.1.3
netappnext_generation_application_programming_interface
-
𝑥
= Vulnerable software versions
Debian logo
Debian Releases
Debian Product
Codename
npm
bullseye
no-dsa
buster
no-dsa
bookworm
9.2.0~ds1-1
fixed
sid
9.2.0~ds1-3
fixed
trixie
9.2.0~ds1-3
fixed
Ubuntu logo
Ubuntu Releases
Ubuntu Product
Codename
npm
noble
needed
mantic
ignored
lunar
ignored
kinetic
ignored
jammy
needed
impish
ignored
hirsute
ignored
focal
not-affected
bionic
not-affected
xenial
not-affected
trusty
not-affected