osv-2020-530
Vulnerability from osv_ossfuzz
Published
2020-07-01 00:00
Modified
2022-04-13 03:04
Summary
Stack-buffer-overflow in ares_parse_aaaa_reply
Details

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

Crash type: Stack-buffer-overflow WRITE 4
Crash state:
ares_parse_aaaa_reply
ares-test-fuzz.c
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "c-ares"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "7d3591ee8a1a63e7748e68e6d880bd1763a32885"
            },
            {
              "fixed": "b949cc3ddfbeb1b3fba571fb53b186b645e66e9c"
            }
          ],
          "repo": "https://github.com/c-ares/c-ares.git",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15459\n\n```\nCrash type: Stack-buffer-overflow WRITE 4\nCrash state:\nares_parse_aaaa_reply\nares-test-fuzz.c\n```\n",
  "id": "OSV-2020-530",
  "modified": "2022-04-13T03:04:36.401229Z",
  "published": "2020-07-01T00:00:14.958697Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15459"
    }
  ],
  "summary": "Stack-buffer-overflow in ares_parse_aaaa_reply"
}


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.