osv-2020-150
Vulnerability from osv_ossfuzz
Published
2020-06-24 01:51
Modified
2022-04-13 03:04
Summary
Segv on unknown address in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
Details

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

Crash type: Segv on unknown address
Crash state:
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<ch
wabt::BinaryReaderIR::OnDataSymbol

{
  "affected": [
    {
      "ecosystem_specific": {
        "fixed_range": "a5a9b341b7fb7aa66427d4701871d2b3c73bcc87:d087e702d520207871ae82c58461fb08d58af187"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "wabt"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "ac29d4f571f54ce3c99243048ebdac6cfe6cc671"
            },
            {
              "fixed": "d087e702d520207871ae82c58461fb08d58af187"
            }
          ],
          "repo": "https://github.com/WebAssembly/wabt",
          "type": "GIT"
        }
      ],
      "versions": [
        "1.0.14",
        "1.0.15"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20457\n\n```\nCrash type: Segv on unknown address\nCrash state:\nstd::__1::basic_string\u003cchar, std::__1::char_traits\u003cchar\u003e, std::__1::allocator\u003cch\nstd::__1::basic_string\u003cchar, std::__1::char_traits\u003cchar\u003e, std::__1::allocator\u003cch\nwabt::BinaryReaderIR::OnDataSymbol\n```\n",
  "id": "OSV-2020-150",
  "modified": "2022-04-13T03:04:37.943567Z",
  "published": "2020-06-24T01:51:16.354141Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20457"
    }
  ],
  "summary": "Segv on unknown address in std::__1::basic_string\u003cchar, std::__1::char_traits\u003cchar\u003e, std::__1::allocator\u003cch"
}


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…