CVE-2021-43616

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

Affected Software

4 affected components
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

Event History

Nov 13, 2021
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverity
Disputed
06:15 PM
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2021-43616?

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.

2

What is the severity of CVE-2021-43616?

The severity of CVE-2021-43616 is critical with a severity value of 9.8.

3

How does CVE-2021-43616 make it easier for attackers?

CVE-2021-43616 makes it easier for attackers to install malware that was supposed to be blocked by the package-lock.json file.

4

Which versions of npm are affected by CVE-2021-43616?

Versions of npm 7.x and 8.x through 8.1.3 are affected by CVE-2021-43616.

5

How can I fix the vulnerability CVE-2021-43616?

To fix CVE-2021-43616, it is recommended to update npm to a version higher than 8.1.3.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203