osv-2025-363
Vulnerability from osv_ossfuzz
Published
2025-05-14 00:03
Modified
2025-05-14 00:03
Summary
Heap-buffer-overflow in jv_string_vfmt
Details

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

Crash type: Heap-buffer-overflow READ 2
Crash state:
jv_string_vfmt
jv_string_fmt
jv_get
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "9ac6ddae2266c6c19f8599c5ad5fc67e3bc7c9f4:c6e041699d8cd31b97375a2596217aff2cfca85b",
        "introduced_range": "98a206964d59143c6ed9189b91cdb34af1ae5071:bfb7fd570f521ef832fe1c3bca0e05abd398284c"
      },
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "jq",
        "purl": "pkg:generic/jq"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "13353515bd3aedf84c6e6ebfb726563ae84db778"
            },
            {
              "fixed": "c6e041699d8cd31b97375a2596217aff2cfca85b"
            }
          ],
          "repo": "https://github.com/jqlang/jq",
          "type": "GIT"
        }
      ],
      "versions": [
        "jq-1.7.1"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=417323384\n\n```\nCrash type: Heap-buffer-overflow READ 2\nCrash state:\njv_string_vfmt\njv_string_fmt\njv_get\n```\n",
  "id": "OSV-2025-363",
  "modified": "2025-05-14T00:03:23.389224Z",
  "published": "2025-05-14T00:03:23.388719Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=417323384"
    }
  ],
  "schema_version": "1.6.0",
  "summary": "Heap-buffer-overflow in jv_string_vfmt"
}


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.