osv-2025-230
Vulnerability from osv_ossfuzz
Published
2025-03-22 00:05
Modified
2025-03-22 00:05
Summary
Heap-buffer-overflow in wasm_loader_prepare_bytecode
Details

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

Crash type: Heap-buffer-overflow WRITE 8
Crash state:
wasm_loader_prepare_bytecode
load_from_sections
wasm_loader_load
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "79f26a96a47bbce8a9f17ba284be4625eca8e265:9aaf3599ec69469f6ab3b4373bfb0d8e6b3345b9",
        "introduced_range": "c30e65ba5d2bb4c1b96e23dfaa74e498fc3ac3a3:06ea960e76d49fcab7342541bde2329e25287520"
      },
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "wamr",
        "purl": "pkg:generic/wamr"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "efa8019bdba89de121f14d84484cecbf023df879"
            },
            {
              "fixed": "9aaf3599ec69469f6ab3b4373bfb0d8e6b3345b9"
            }
          ],
          "repo": "https://github.com/bytecodealliance/wasm-micro-runtime",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=404921047\n\n```\nCrash type: Heap-buffer-overflow WRITE 8\nCrash state:\nwasm_loader_prepare_bytecode\nload_from_sections\nwasm_loader_load\n```\n",
  "id": "OSV-2025-230",
  "modified": "2025-03-22T00:05:22.916485Z",
  "published": "2025-03-22T00:05:22.916187Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=404921047"
    }
  ],
  "schema_version": "1.6.0",
  "summary": "Heap-buffer-overflow in wasm_loader_prepare_bytecode"
}


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.