GHSA-HXXF-Q3W9-4XGW

Vulnerability from github – Published: 2018-07-12 19:52 – Updated: 2021-09-14 17:35
VLAI
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.

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

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "eslint-scope"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.7.2"
            },
            {
              "fixed": "3.7.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.7.2"
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "eslint-config-eslint"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.0.2"
            },
            {
              "fixed": "6.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.0.2"
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-506"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-06-16T21:41:33Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "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",
  "id": "GHSA-hxxf-q3w9-4xgw",
  "modified": "2021-09-14T17:35:41Z",
  "published": "2018-07-12T19:52:02Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Malicious Package in eslint-scope"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.