GHSA-2HPJ-G53M-9GJ6

Vulnerability from github – Published: 2019-02-18 23:58 – Updated: 2023-09-08 20:52
VLAI?
Summary
closure-util downloads Resources over HTTP
Details

Affected versions of closure-util insecurely download an executable over an unencrypted HTTP connection.

In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running closure-util.

Recommendation

To mitigate this issue: 1. Install the package using npm's --ignore-scripts flag. 2. Navigate to the package directory, and open default-config.json in a text editor 3. Change the download URLs in the compiler_url and library_url to https equivalents 4. run npm i in the package directory.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "closure-util"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "2.0.0-beta.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2016-10583"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-311"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-06-16T20:52:08Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "Affected versions of `closure-util` insecurely download an executable over an unencrypted HTTP connection. \n\nIn scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `closure-util`.\n\n\n## Recommendation\n\nTo mitigate this issue:\n1. Install the package using npm\u0027s `--ignore-scripts` flag.\n2. Navigate to the package directory, and open `default-config.json` in a text editor\n3. Change the download URLs in the `compiler_url` and `library_url` to `https` equivalents\n4. run `npm i` in the package directory.",
  "id": "GHSA-2hpj-g53m-9gj6",
  "modified": "2023-09-08T20:52:07Z",
  "published": "2019-02-18T23:58:03Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2016-10583"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-2hpj-g53m-9gj6"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/165"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "closure-util downloads Resources over HTTP"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…