CVE-2021-436169.0CriticalCWE-345

CVE-2021-43616: Npmjs vulnerability

Npmjs · Npm

Vendor fix available · Affected: Npmjs · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.6%probability of exploitation in the next 30 days

85th percentile

050100

Higher than 85% of scored CVEs

9.0CriticalCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Insufficient Verification of Data Authenticity · Cryptography
Vendor: Npmjs
Published: November 2021
Band: Possible (1 to 10%), November 2021

CoverageNo articles yet

No CyberSIXT article names CVE-2021-43616 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.