osv-2024-389
Vulnerability from osv_ossfuzz
Published
2024-04-30 00:14
Modified
2024-04-30 00:14
Summary
Heap-buffer-overflow in JS_CallInternal
Details

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67611

Crash type: Heap-buffer-overflow READ 1
Crash state:
JS_CallInternal
async_func_resume
js_async_function_resume
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "db9dbd0a2b6d115c9ef3c0dc37e0c669ef4844e4:d378a9f3a583cb787c390456e27276d0ee377d23",
        "introduced_range": "3ab1c2b3148d1c70181607002aac23ecdd2ad482:3c2cfabfc74e8af1f21db93884ed1ad9b6388a8c"
      },
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "quickjs",
        "purl": "pkg:generic/quickjs"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "bd0b7048de817045a5396fbfee893687521f16de"
            },
            {
              "fixed": "d378a9f3a583cb787c390456e27276d0ee377d23"
            }
          ],
          "repo": "https://github.com/bellard/quickjs",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67611\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\nJS_CallInternal\nasync_func_resume\njs_async_function_resume\n```\n",
  "id": "OSV-2024-389",
  "modified": "2024-04-30T00:14:11.246314Z",
  "published": "2024-04-30T00:14:11.245997Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67611"
    }
  ],
  "schema_version": "1.6.0",
  "summary": "Heap-buffer-overflow in JS_CallInternal"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.



Detection rules are retrieved from Rulezet.