Dependency substitution via missing lockfile validation
Published Nov 13, 2021 · Updated Aug 4, 2024
Insufficient lockfile validation in npm CLI 7.x and 8.x through 8.1.3 allows attackers to install dependencies not pinned by the lockfile. The npm ci path begins installation without comparing package.json dependency specifications against package-lock.json, so mismatched versions are installed instead of causing an error. Reachability requires write access to or social engineering of package.json, and npm disputes that this trust-boundary failure is a vulnerability.
Summary
What happened
Insufficient lockfile validation in npm CLI 7.x and 8.x through 8.1.3 allows attackers to install dependencies not pinned by the lockfile. The npm ci path begins installation without comparing package.json dependency specifications against package-lock.json, so mismatched versions are installed instead of causing an error. Reachability requires write access to or social engineering of package.json, and npm disputes that this trust-boundary failure is a vulnerability.
The record
- CVE
- CVE-2021-43616
- Published
- Nov 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1195.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- icatalina CVE-2021-43616 demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo