CVE-2021-43616
48Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9epss 2.5%
from disclosure to weapon2 days
Published on NVDNov 13
1st PoC+2d
exploitation probability
2.5%top 17% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N
Affected products
n/a · n/apublic PoCs found — 1
githubgithub.com/icatalina/CVE-2021-43616★ 3⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://docs.npmjs.com/cli/v7/commands/npm-cihttps://docs.npmjs.com/cli/v8/commands/npm-cihttps://github.com/icatalina/CVE-2021-43616https://github.com/npm/cli/commit/457e0ae61bbc55846f5af44afa4066921923490fhttps://github.com/npm/cli/issues/2701https://github.com/npm/cli/issues/2701#issuecomment-972900511https://github.com/npm/cli/issues/2701#issuecomment-979054224https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NXNVFKOF5ZYH5NIRWHKN6O6UBCHDV6FE/https://medium.com/cider-sec/this-time-we-were-lucky-85c0dcac94a0https://security.netapp.com/advisory/ntap-20211210-0002/