osv-2020-357
Vulnerability from osv_ossfuzz
Published
2020-07-01 00:00
Modified
2022-04-13 03:04
Summary
Heap-buffer-overflow in r_read_le32
Details

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
r_read_le32
dex_method_signature2
dex_parse_debug_item

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "radare2"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "b022c9533482a8f1c9ae825ced5c1a3e251837d9"
            },
            {
              "fixed": "55ec5cc1938fba3c506e87c5314630f1f0736a15"
            }
          ],
          "repo": "https://github.com/radare/radare2",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12685\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\nr_read_le32\ndex_method_signature2\ndex_parse_debug_item\n```\n",
  "id": "OSV-2020-357",
  "modified": "2022-04-13T03:04:36.567512Z",
  "published": "2020-07-01T00:00:04.961488Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12685"
    }
  ],
  "summary": "Heap-buffer-overflow in r_read_le32"
}


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…