GHSA-hxxf-q3w9-4xgw: Eslint scope Malicious Package Vulnerability

CRITICAL
Share
CVSS 9.1
CWE-506
Published
Advisory Summary

GHSA-hxxf-q3w9-4xgw is a CRITICAL (CVSS 9.1) malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting Eslint scope libraries in the npm ecosystem. The issue involves malicious package in eslint-scope. Remediation is available by upgrading affected packages to version 3.7.3, 6.0.0.

GHSA-hxxf-q3w9-4xgw at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-hxxf-q3w9-4xgw
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Eslint scope
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.1

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:N).

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 None (A:N)

How to Fix GHSA-hxxf-q3w9-4xgw

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

eslint-scope fixed: 3.7.3 
npm install eslint-scope@3.7.3
eslint-config-eslint fixed: 6.0.0 
npm install eslint-config-eslint@6.0.0
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 eslint-scope

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-hxxf-q3w9-4xgw, inspect your project dependencies using npm:

npm ls eslint-scope

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

Note: The npm ls eslint-scope 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-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Eslint scope, 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

Version 3.7.2 of `eslint-scope` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to 2 remote servers. ## Recommendation The best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens

GHSA-hxxf-q3w9-4xgw Affected Eslint scope Versions

2 component(s)
Fixed Versions:
3.7.36.0.0
Product / Package Ecosystem Affected Versions Fixed Version
eslint-scope
npm/eslint-scope
npm
≥ 3.7.2
< 3.7.3
All 1 versions
3.7.2
3.7.3
eslint-config-eslint
npm/eslint-config-eslint
npm
≥ 5.0.2
< 6.0.0
All 1 versions
5.0.2
6.0.0

References

Eslint scope Source Repository REPOSITORY
https://github.com/eslint/eslint-scope/issues/39
eslint.org/blog/2018/07/postmo... WEB
https://eslint.org/blog/2018/07/postmortem-for-malicious-package-publishes
GitHub Advisory / Wiki ADVISORY
https://github.com/advisories/GHSA-hxxf-q3w9-4xgw
Eslint scope Source Repository REPOSITORY
https://github.com/eslint/eslint-scope
snyk.io/vuln/snyk-js-eslint... WEB
https://snyk.io/vuln/SNYK-JS-ESLINTSCOPE-11120
www.npmjs.com/advisories/673 WEB
https://www.npmjs.com/advisories/673

Frequently Asked Questions

What is GHSA-hxxf-q3w9-4xgw?
GHSA-hxxf-q3w9-4xgw is a security vulnerability in Eslint scope involving Malicious Package in eslint-scope under CWE-506: Embedded Malicious Code.
Which Eslint scope versions are affected?
Affected versions include releases prior to 3.7.3, 6.0.0 across affected packages: eslint-scope, eslint-config-eslint.
What version fixes GHSA-hxxf-q3w9-4xgw?
Upgrading to 3.7.3, 6.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is eslint-scope affected?
Yes, eslint-scope is affected in releases prior to 3.7.3. Upgrade your dependency to 3.7.3 or later.
Is eslint-config-eslint affected?
Yes, eslint-config-eslint is affected in releases prior to 6.0.0. Upgrade your dependency to 6.0.0 or later.
What is the CVSS score of GHSA-hxxf-q3w9-4xgw?
GHSA-hxxf-q3w9-4xgw has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with GHSA-hxxf-q3w9-4xgw?
GHSA-hxxf-q3w9-4xgw is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check npm dependencies for GHSA-hxxf-q3w9-4xgw?
Run the dependency tree command: 'npm ls eslint-scope'. 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-hxxf-q3w9-4xgw",
  "modified" : "2021-09-14T17:35:41Z",
  "published" : "2018-07-12T19:52:02Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in eslint-scope",
  "details" : "Version 3.7.2 of `eslint-scope` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to 2 remote servers.\n\n\n## Recommendation\n\nThe best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "eslint-scope"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.7.2"
      }, {
        "fixed" : "3.7.3"
      } ]
    } ],
    "versions" : [ "3.7.2" ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "eslint-config-eslint"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.2"
      }, {
        "fixed" : "6.0.0"
      } ]
    } ],
    "versions" : [ "5.0.2" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/eslint/eslint-scope/issues/39"
  }, {
    "type" : "WEB",
    "url" : "https://eslint.org/blog/2018/07/postmortem-for-malicious-package-publishes"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-hxxf-q3w9-4xgw"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/eslint/eslint-scope"
  }, {
    "type" : "WEB",
    "url" : "https://snyk.io/vuln/SNYK-JS-ESLINTSCOPE-11120"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/673"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-06-16T21:41:33Z",
    "nvd_published_at" : null
  }
}