osv-2022-105
Vulnerability from osv_ossfuzz
Published
2022-01-31 00:00
Modified
2022-04-13 03:04
Summary
Heap-buffer-overflow in parse_object
Details

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

Crash type: Heap-buffer-overflow READ 4
Crash state:
parse_object
parse_object
parse_object
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "libplist",
        "purl": "pkg:generic/libplist"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "31a353b57152e7b44254853520a06568a4a91dce"
            },
            {
              "fixed": "924ba961d68f6833f617fd3ad03c40f63f287142"
            }
          ],
          "repo": "https://github.com/libimobiledevice/libplist",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44199\n\n```\nCrash type: Heap-buffer-overflow READ 4\nCrash state:\nparse_object\nparse_object\nparse_object\n```\n",
  "id": "OSV-2022-105",
  "modified": "2022-04-13T03:04:39.854288Z",
  "published": "2022-01-31T00:00:44.191266Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44199"
    }
  ],
  "schema_version": "1.2.0",
  "summary": "Heap-buffer-overflow in parse_object"
}


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.