osv-2020-65
Vulnerability from osv_ossfuzz
Published
2020-06-24 01:51
Modified
2022-04-13 03:04
Summary
Heap-use-after-free in std::__1::vector<unsigned long, std::__1::allocator<unsigned long> >::begin
Details

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

Crash type: Heap-use-after-free READ 8
Crash state:
std::__1::vector<unsigned long, std::__1::allocator<unsigned long> >::begin
perfetto::trace_processor::TrackTracker::ResolveDescriptorTrack
perfetto::trace_processor::TrackTracker::GetDescriptorTrackImpl
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "perfetto"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "e5a041472ebe8e99532d0dfdcc8970bf4714ee19"
            },
            {
              "fixed": "0df72fe5d206a73023cc970840869021e249f647"
            }
          ],
          "repo": "https://android.googlesource.com/platform/external/perfetto/",
          "type": "GIT"
        }
      ],
      "versions": [
        "platform-tools-30.0.1"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21908\n\n```\nCrash type: Heap-use-after-free READ 8\nCrash state:\nstd::__1::vector\u003cunsigned long, std::__1::allocator\u003cunsigned long\u003e \u003e::begin\nperfetto::trace_processor::TrackTracker::ResolveDescriptorTrack\nperfetto::trace_processor::TrackTracker::GetDescriptorTrackImpl\n```\n",
  "id": "OSV-2020-65",
  "modified": "2022-04-13T03:04:41.932323Z",
  "published": "2020-06-24T01:51:12.508705Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21908"
    }
  ],
  "summary": "Heap-use-after-free in std::__1::vector\u003cunsigned long, std::__1::allocator\u003cunsigned long\u003e \u003e::begin"
}


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.