CVE-2022-0841

Public Exploit
OS Command Injection in ljharb/npm-lockfile

Description

OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.

Category

9.8
CVSS
Severity: Critical
CVSS 3.1 •
CVSS 3.0 •
CVSS 2.0 •
EPSS 1.84% Top 20%
Third-Party Advisory github.com Third-Party Advisory huntr.dev
Affected: ljharb ljharb/npm-lockfile
Published at:
Updated at:

References

Link Tags
https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1 exploit third party advisory patch
https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2022-0841?
CVE-2022-0841 has been scored as a critical severity vulnerability.
How to fix CVE-2022-0841?
To fix CVE-2022-0841, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-0841 being actively exploited in the wild?
It is possible that CVE-2022-0841 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-0841?
CVE-2022-0841 affects ljharb ljharb/npm-lockfile.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.