CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2021 · Npmjs

CVE-2021-43616
Npmjs Npm vulnerability

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.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Npm, Next Generation Application Programming Interface, Fedora. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Npmjs Npm runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Npmjs products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.