osv-2025-528
Vulnerability from osv_ossfuzz
Published
2025-07-07 00:10
Modified
2025-07-07 00:10
Summary
Heap-buffer-overflow in xmlnode_parser_structural_error_libxml
Details

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

Crash type: Heap-buffer-overflow WRITE 4
Crash state:
xmlnode_parser_structural_error_libxml
__xmlRaiseError
xmlParseAttValueInternal
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "748de3eed506a515840fcea85fb1c0c22c170c2a:734e55f3cfed1adbb51bf6cb5c65b4c1197b7089",
        "introduced_range": "unknown:5997a4fc09163c1baa186f5a9d00c4c8668a72b1"
      },
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "pidgin",
        "purl": "pkg:generic/pidgin"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5997a4fc09163c1baa186f5a9d00c4c8668a72b1"
            },
            {
              "fixed": "734e55f3cfed1adbb51bf6cb5c65b4c1197b7089"
            }
          ],
          "repo": "https://github.com/google/fuzzing",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=429429092\n\n```\nCrash type: Heap-buffer-overflow WRITE 4\nCrash state:\nxmlnode_parser_structural_error_libxml\n__xmlRaiseError\nxmlParseAttValueInternal\n```\n",
  "id": "OSV-2025-528",
  "modified": "2025-07-07T00:10:42.902766Z",
  "published": "2025-07-07T00:10:42.902465Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=429429092"
    }
  ],
  "schema_version": "1.6.0",
  "summary": "Heap-buffer-overflow in xmlnode_parser_structural_error_libxml"
}


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.