Skip to content
Fencer Intel
low 3.8

CVE-2022-0841 json

OS Command Injection in ljharb/npm-lockfile

published 4y ago modified 4mo ago also GHSA-cr6m-62pq-hmqh , EUVD-2022-1409

cvss
3.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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

Patch / fix

  • npm npm-lockfile 2.0.5

Is CVE-2022-0841 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-0841 updated cvss 5.3

npm-lockfile: os command injection

  • Red Hat Enterprise Linux 8 npm, nodejs, cockpit, cockpit-ws, 389-ds-base, cockpit-pcp, +17 more Red Hat Software Collections rh-nodejs12-npm, rh-nodejs14-npm, rh-nodejs12-nodejs, rh-nodejs14-nodejs, rh-nodejs14-nodejs-full-i18n
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.51% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 3.8 CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm npm-lockfile
>=2.0.3, <2.0.5
2.0.5

Affected products

  • ljharb ljharb/npm-lockfile

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.