Vulnerability-Lookup

GHSA-R4JG-5V89-9V62

Vulnerability from github – Published: 2022-11-08 20:48 – Updated: 2022-11-09 22:35

Withdrawn 2022-11-09

Summary

Withdrawn: Octocat.js vulnerable to code injection

Details

Withdrawn

This advisory has been withdrawn because it is a test.

Original Description

Impact

Users can include their own images for accessories via provided URLs. These URLs are not validated and can result in execution of injected code.

Patches

This vulnerability was fixed in version 1.2 of octocat.js

Workarounds

Directly exposing rendered images to a website can introduce the vulnerability to users. To avoid, writing an image to disk then using that image in an image element in HTML mitigates the risk.

References

To render the file correctly, see documentation at readme.md

For more information

If you have any questions or comments about this advisory: * Open an issue in the octo.js repository

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "octocat.js"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-39390"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-74",
      "CWE-94"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-11-08T20:48:49Z",
    "nvd_published_at": "2022-11-09T01:15:00Z",
    "severity": "HIGH"
  },
  "details": "## Withdrawn\n\nThis advisory has been withdrawn because it is a test.\n\n## Original Description\n\n### Impact\nUsers can include their own images for accessories via provided URLs. These URLs are not validated and can result in execution of injected code.\n\n### Patches\nThis vulnerability was fixed in version 1.2 of octocat.js\n\n### Workarounds\nDirectly exposing rendered images to a website can introduce the vulnerability to users. To avoid, writing an image to disk then using that image in an image element in HTML mitigates the risk.\n\n### References\nTo render the file correctly, see documentation at `readme.md`\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the octo.js repository](http://github.com/octocademy/octocat.js/issues)\n",
  "id": "GHSA-r4jg-5v89-9v62",
  "modified": "2022-11-09T22:35:46Z",
  "published": "2022-11-08T20:48:49Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/octocademy/octocat.js/security/advisories/GHSA-r4jg-5v89-9v62"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-39390"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/octocademy/octocat.js"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Withdrawn: Octocat.js vulnerable to code injection",
  "withdrawn": "2022-11-09T22:35:46Z"
}

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.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted