osv-2017-16
Vulnerability from osv_ossfuzz
Published
2021-01-13 00:00
Modified
2023-01-04 05:25
Summary
Heap-buffer-overflow in file_strncmp
Details

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
file_strncmp
magiccheck
match
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "file"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "17f892b32cc92f7505f02d198142c1a57204582f"
            },
            {
              "fixed": "3590556273652e71251fa79890eeb959ef02d8d8"
            },
            {
              "fixed": "77a7041fae5b7c8cc3844bcd29b88a193b8e3752"
            }
          ],
          "repo": "https://github.com/file/file.git",
          "type": "GIT"
        }
      ],
      "versions": [
        "FILE5_30"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=750\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\nfile_strncmp\nmagiccheck\nmatch\n```\n",
  "id": "OSV-2017-16",
  "modified": "2023-01-04T05:25:43.259245Z",
  "published": "2021-01-13T00:00:27.841127Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=750"
    }
  ],
  "summary": "Heap-buffer-overflow in file_strncmp"
}


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.