osv-2025-437
Vulnerability from osv_ossfuzz
Published
2025-06-05 00:18
Modified
2025-06-05 00:18
Summary
Heap-buffer-overflow in mmcall
Details

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

Crash type: Heap-buffer-overflow WRITE 8
Crash state:
mmcall
lj_meta_tget
lj_vmeta_tgetv
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "introduced_range": "b33f17b25de6bcbe3ebc236250976e4a0250e75e:c10c62927e4cba52cfc44103fc1e21c9d6606fb2"
      },
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "tarantool",
        "purl": "pkg:generic/tarantool"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "46ee17556f2e1a7d65f20383f5e0ff3381998a27"
            },
            {
              "fixed": "8c7cfb1cd0b3f5ce1d5b181403f68f7aaf657d9a"
            }
          ],
          "repo": "https://github.com/tarantool/tarantool",
          "type": "GIT"
        }
      ],
      "versions": [
        "3.3.0",
        "3.3.1",
        "3.3.1-entrypoint",
        "3.3.2",
        "3.3.2-entrypoint",
        "3.3.3-entrypoint",
        "3.4.0",
        "3.4.0-entrypoint",
        "3.4.1-entrypoint",
        "3.5.0-entrypoint"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=421943174\n\n```\nCrash type: Heap-buffer-overflow WRITE 8\nCrash state:\nmmcall\nlj_meta_tget\nlj_vmeta_tgetv\n```\n",
  "id": "OSV-2025-437",
  "modified": "2025-06-05T00:18:59.403189Z",
  "published": "2025-06-05T00:18:59.402795Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=421943174"
    }
  ],
  "schema_version": "1.6.0",
  "summary": "Heap-buffer-overflow in mmcall"
}


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.