CVE-2021-43616
** DISPUTED ** 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2021-43616?
CVE-2021-43616 is a vulnerability that allows the npm ci command in npm 7.x and 8.x through 8.1.3 to proceed with an installation even if dependency information in package-lock.json differs from package.json.
What is the severity of CVE-2021-43616?
The severity of CVE-2021-43616 is critical with a severity value of 9.8.
How does CVE-2021-43616 make it easier for attackers?
CVE-2021-43616 makes it easier for attackers to install malware that was supposed to be blocked by the package-lock.json file.
Which versions of npm are affected by CVE-2021-43616?
Versions of npm 7.x and 8.x through 8.1.3 are affected by CVE-2021-43616.
How can I fix the vulnerability CVE-2021-43616?
To fix CVE-2021-43616, it is recommended to update npm to a version higher than 8.1.3.