Vulnerabilities in pkg:npm/npm-lockfile

PACKAGE
Advisory Identifier: GHSA-cr6m-62pq-hmqh
Share
Advisory Summary

CVE-2022-0841 is a CRITICAL (CVSS 9.8) os command injection vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Npm lockfile libraries in the npm ecosystem. The issue involves os command injection in npm-lockfile. Remediation is available by upgrading affected packages to version 2.0.5.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/npm-lockfile

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/npm-lockfile. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-cr6m-62pq-hmqh CVE-2022-0841 CRITICAL OS Command injection in npm-lockfile

CVE-2022-0841 at a Glance

CVE Identifier CVE-2022-0841
GHSA Identifier GHSA-cr6m-62pq-hmqh
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Npm lockfile
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2022-0841

To remediate this vulnerability, upgrade all affected Npm lockfile dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

npm-lockfile fixed: 2.0.5 
npm install npm-lockfile@2.0.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls npm-lockfile

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2022-0841, inspect your project dependencies using npm:

npm ls npm-lockfile

Analyze the terminal output to locate any version of Npm lockfile in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.5), your application is affected.

Note: The npm ls npm-lockfile command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Npm lockfile, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2022-0841 Affected Npm lockfile Versions

1 component(s)
Fixed Versions:
2.0.5
Product / Package Ecosystem Affected Versions Fixed Version
npm-lockfile
npm/npm-lockfile
npm
≥ 2.0.3
< 2.0.5
2.0.5

References

NVD — CVE-2022-0841 NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-0841
Security Fix Commit FIX COMMIT
https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8
Npm lockfile Source Repository REPOSITORY
https://github.com/ljharb/npm-lockfile
huntr.dev/bounties/4f806dc9-2... WEB
https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1

Frequently Asked Questions

What is CVE-2022-0841?
CVE-2022-0841 is a security vulnerability in Npm lockfile involving OS Command injection in npm-lockfile under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Npm lockfile versions are affected?
Affected versions include releases prior to 2.0.5 across affected packages: npm-lockfile.
What version fixes CVE-2022-0841?
Upgrading to 2.0.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is npm-lockfile affected?
Yes, npm-lockfile is affected in releases prior to 2.0.5. Upgrade your dependency to 2.0.5 or later.
What is the CVSS score of CVE-2022-0841?
CVE-2022-0841 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2022-0841?
CVE-2022-0841 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check npm dependencies for CVE-2022-0841?
Run the dependency tree command: 'npm ls npm-lockfile'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cr6m-62pq-hmqh",
  "modified" : "2022-04-04T21:37:38Z",
  "published" : "2022-03-04T00:00:18Z",
  "aliases" : [ "CVE-2022-0841" ],
  "summary" : "OS Command injection in npm-lockfile",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "npm-lockfile"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.3"
      }, {
        "fixed" : "2.0.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-0841"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ljharb/npm-lockfile/commit/bfdb84813260f0edbf759f2fde1e8c816c1478b8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ljharb/npm-lockfile"
  }, {
    "type" : "WEB",
    "url" : "https://huntr.dev/bounties/4f806dc9-2ecd-4e79-997e-5292f1bea9f1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-78" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-03-04T21:20:11Z",
    "nvd_published_at" : "2022-03-03T16:15:00Z"
  }
}