osv-2025-266
Vulnerability from osv_ossfuzz
Published
2025-04-08 00:17
Modified
2026-01-27 14:24
Summary
Heap-buffer-overflow in lj_buf_ruleb128
Details

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
lj_buf_ruleb128
lj_bcread
cpparser
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "introduced_range": "f40901fbc98e46e0f4c276cbb51ffaf1abbbfebb:43aa0bf45ef18f76b312fabf3d3842d81a970bae"
      },
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "tarantool",
        "purl": "pkg:generic/tarantool"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "8ad443de995a7800906718925ce6c9162d80c4a9"
            }
          ],
          "repo": "https://github.com/tarantool/tarantool",
          "type": "GIT"
        }
      ],
      "versions": [
        "3.4.0",
        "3.4.1-entrypoint",
        "3.5.0-entrypoint",
        "3.4.1",
        "3.4.2-entrypoint",
        "3.5.0",
        "3.5.1-entrypoint",
        "3.6.0-entrypoint",
        "3.4.2",
        "3.4.3-entrypoint",
        "3.5.1",
        "3.5.2-entrypoint",
        "3.6.0",
        "3.6.1-entrypoint",
        "3.7.0-entrypoint",
        "3.6.1",
        "3.6.2-entrypoint"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=408513931\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\nlj_buf_ruleb128\nlj_bcread\ncpparser\n```\n",
  "id": "OSV-2025-266",
  "modified": "2026-01-27T14:24:04.437262Z",
  "published": "2025-04-08T00:17:06.279554Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=408513931"
    }
  ],
  "schema_version": "1.6.0",
  "summary": "Heap-buffer-overflow in lj_buf_ruleb128"
}


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.