osv-2018-99
Vulnerability from osv_ossfuzz
Published
2021-01-13 00:00
Modified
2022-04-13 03:04
Summary
Heap-buffer-overflow in git__strntol64
Details

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
git__strntol64
git_signature__parse
git_commit__parse_raw
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "libgit2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3db9aa6f79711103a331a2bbbd044a3c37d4f136"
            },
            {
              "fixed": "41863a00f0d811c659c9ba87ae2cc0c3aae5a77f"
            }
          ],
          "repo": "https://github.com/libgit2/libgit2",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11173\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\ngit__strntol64\ngit_signature__parse\ngit_commit__parse_raw\n```\n",
  "id": "OSV-2018-99",
  "modified": "2022-04-13T03:04:35.208725Z",
  "published": "2021-01-13T00:00:43.443325Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11173"
    }
  ],
  "summary": "Heap-buffer-overflow in git__strntol64"
}


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.