osv-2021-440
Vulnerability from osv_ossfuzz
Published
2021-02-24 00:00
Modified
2022-04-13 03:28
Summary
Heap-buffer-overflow in H5MM_memcpy
Details

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

Crash type: Heap-buffer-overflow WRITE 4
Crash state:
H5MM_memcpy
H5MM_malloc
H5C_load_entry

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "matio"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1ce8f2d1845ecdde19a35605cabdbb884776d52d"
            },
            {
              "fixed": "cddcdad17864c4b95ead23581047b41636f180a3"
            },
            {
              "fixed": "b89ed176f27c71657587d231794bee09d0461d08"
            }
          ],
          "repo": "git://git.code.sf.net/p/matio/matio",
          "type": "GIT"
        }
      ],
      "versions": [
        "v1.5.20",
        "v1.5.21"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31265\n\n```\nCrash type: Heap-buffer-overflow WRITE 4\nCrash state:\nH5MM_memcpy\nH5MM_malloc\nH5C_load_entry\n```\n",
  "id": "OSV-2021-440",
  "modified": "2022-04-13T03:28:23.858966Z",
  "published": "2021-02-24T00:00:05.141282Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=31265"
    }
  ],
  "summary": "Heap-buffer-overflow in H5MM_memcpy"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…