CVE-2021-43616

Critical

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.

SeverityCritical
CVSS9.0
Exploit probability—
ProductNpm
PublishedNov 13, 2021
First seenNov 13, 2021

How to fix

Affected products

ProductAffected versionsFixed in
npmjs npm7.0.0 ≤ v ≤ 7.24.2, 8.0.0 ≤ v ≤ 8.1.3—
netapp next_generation_application_programming_interfaceNo range specified—
fedoraproject fedora35—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.