Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2021-43616

9.0 · CRITICAL

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.

Published Nov 13, 2021CWE-345EPSS 2.72%

Overview

CVE-2021-43616 is a critical-severity vulnerability. It was published on November 13, 2021 and has a CVSS 3.1 base score of 9.0 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refdocs.npmjs.com/cli/v7/commands/npm-ciRefdocs.npmjs.com/cli/v8/commands/npm-ciGitHubgithub.com/icatalina/CVE-2021-43616GitHubgithub.com/npm/cli/commit/457e0ae61bbc55846f5af44afa4066921923490fGitHubgithub.com/npm/cli/issues/2701GitHubgithub.com/npm/cli/issues/2701#issuecomment-972900511GitHubgithub.com/npm/cli/issues/2701#issuecomment-979054224Reflists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NXNVFKOF5ZYH5NIRWHKN6O6UBCHDV6FE/Refmedium.com/cider-sec/this-time-we-were-lucky-85c0dcac94a0Refsecurity.netapp.com/advisory/ntap-20211210-0002/

How CyberStrike helps

Frequently asked questions

What is CVE-2021-43616?

CVE-2021-43616 is a critical-severity vulnerability. It was published on November 13, 2021 and has a CVSS 3.1 base score of 9.0 (CRITICAL).

How severe is CVE-2021-43616?

This vulnerability has a CVSS 3.1 base score of 9.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2021-43616?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2021-43616?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2021-43616 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2021

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999