{"id":"CVE-2022-0841","aliases":["EUVD-2022-1409","GHSA-cr6m-62pq-hmqh"],"status":"published","title":"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.","severity":{"version":"3.0","score":3.8,"vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-08","score":0.02513,"percentile":0.84901,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-78"],"published":"2022-03-03T15:50:10Z","modified":"2026-10-28T02:30:38Z","fixes":[{"ecosystem":"npm","package":"npm-lockfile","fixed_in":["2.0.5"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"npm-lockfile","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.3"},{"fixed":"2.0.5"}]}]},{"source":"osv","ecosystem":"npm","package":"npm-lockfile","ranges":[{"type":"SEMVER","events":[{"introduced":"2.0.3"},{"fixed":"2.0.5"}]}]}],"products":[{"vendor":"ljharb","product":"ljharb/npm-lockfile"},{"vendor":"npm-lockfile_project","product":"npm-lockfile"}],"references":[{"url":"https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1","tags":["x_refsource_CONFIRM","x_transferred","Exploit","Patch","Third Party Advisory","web"]},{"url":"https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-0841","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-cr6m-62pq-hmqh"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/0xxx/CVE-2022-0841.json","tags":["advisory"]},{"url":"https://github.com/ljharb/npm-lockfile","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2022-0841","title":"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.","status":"published","published":"2022-03-03T15:50:10Z","modified":"2024-08-02T23:40:04.446Z","cvss":[{"version":"3.0","score":3.8,"vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","level":"low","assessor":"cna"}],"cwes":["CWE-78"],"updated_at":"2026-11-02T14:34:41.34666Z"}],"euvd":[{"id":"EUVD-2022-1409","description":"OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.","status":"published","published":"2022-03-03T15:50:10Z","modified":"2024-08-02T23:40:04Z","cvss":[{"version":"3.0","score":3.8,"vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","level":"low"}],"updated_at":"2026-11-03T03:26:03.912978Z"}],"ghsa":[{"id":"GHSA-cr6m-62pq-hmqh","title":"OS Command injection in npm-lockfile","description":"npm-lockfile safely generates an npm lockfile and output it to the filename of your choice. npm-lockfile before 2.0.4 does not santize unsafe external input and invoke sensitive command execution API with the input, causing command injection vulnerability. A fix was released in version 2.0.5.","status":"published","published":"2022-03-04T00:00:18Z","modified":"2023-02-03T05:06:21Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-78"],"updated_at":"2026-11-02T14:36:43.439065Z"}],"nvd":[{"id":"CVE-2022-0841","description":"OS Command Injection in GitHub repository ljharb/npm-lockfile in v2.0.3 and v2.0.4.","status":"published","published":"2022-03-03T16:15:07.863Z","modified":"2026-06-17T04:21:21.17Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"},{"version":"3.0","score":3.8,"vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","level":"low","assessor":"secondary"},{"version":"2.0","score":10,"vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","level":"high","assessor":"primary"}],"cwes":["CWE-78"],"updated_at":"2026-11-02T14:07:12.711288Z"}],"osv":[{"id":"CVE-2022-0841","title":"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.","status":"published","published":"2022-03-03T15:50:10Z","modified":"2026-10-28T02:30:38.155204285Z","cvss":[{"version":"3.0","score":3.8,"vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","level":"low"}],"cwes":["CWE-78"],"updated_at":"2026-11-02T15:44:22.824781Z"},{"id":"GHSA-cr6m-62pq-hmqh","title":"OS Command injection in npm-lockfile","description":"npm-lockfile safely generates an npm lockfile and output it to the filename of your choice. npm-lockfile before 2.0.4 does not santize unsafe external input and invoke sensitive command execution API with the input, causing command injection vulnerability. A fix was released in version 2.0.5.","status":"published","published":"2022-03-04T00:00:18Z","modified":"2023-11-08T04:07:41.089499Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-78"],"updated_at":"2026-11-02T15:46:45.28161Z"}]}}