CVE-2022-0841
CRITICALCVSS 9.8/10EPSS 2.67%
Last modified
CVE-2022-0841 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.. EPSS estimates a 2.67% chance of exploitation in the next 30 days.
Description
OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Npm-Lockfile Project | Npm-Lockfile | 2.0.3 |
| Npm-Lockfile Project | Npm-Lockfile | 2.0.4 |
References
- https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8Patch, Third Party Advisory
- https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1Exploit, Patch, Third Party Advisory
- https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8Patch, Third Party Advisory
- https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1Exploit, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-0841?
OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.
How severe is CVE-2022-0841?
CVE-2022-0841 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 2.67% probability of exploitation in the next 30 days.
How do I fix CVE-2022-0841?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-0835AVEVA System Platform 2020 stores sensitive information in c…5.5
- CVE-2022-0836The SEMA API WordPress plugin before 4.02 does not properly …9.8
- CVE-2022-0837The Amelia WordPress plugin before 1.0.48 does not have prop…5.4
- CVE-2022-0838Cross-site Scripting (XSS) - Reflected in GitHub repository …6.1
- CVE-2022-0839Improper Restriction of XML External Entity Reference in Git…9.8
- CVE-2022-0840The Easy Social Icons WordPress plugin before 3.2.1 does not…4.8
- CVE-2022-0842A blind SQL injection vulnerability in McAfee Enterprise ePo…4.9
- CVE-2022-0843Mozilla developers Kershaw Chang, Ryan VanderMeulen, and Ran…8.8
- CVE-2022-0844Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2022-0845Code Injection in GitHub repository pytorchlightning/pytorch…9.8
- CVE-2022-0846The SpeakOut! Email Petitions WordPress plugin before 2.14.1…9.8
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pi…7.8
Are you affected by CVE-2022-0841?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST