First published: Sat Nov 13 2021(Updated: )
** 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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Npmjs Npm | >=7.0.0<=7.24.2 | |
Npmjs Npm | >=8.0.0<=8.1.3 | |
Netapp Next Generation Application Programming Interface | ||
Fedoraproject Fedora | =35 | |
>=7.0.0<=7.24.2 | ||
>=8.0.0<=8.1.3 | ||
=35 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
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.
The severity of CVE-2021-43616 is critical with a severity value of 9.8.
CVE-2021-43616 makes it easier for attackers to install malware that was supposed to be blocked by the package-lock.json file.
Versions of npm 7.x and 8.x through 8.1.3 are affected by CVE-2021-43616.
To fix CVE-2021-43616, it is recommended to update npm to a version higher than 8.1.3.