osv-2020-1611
Vulnerability from osv_ossfuzz
Published
2020-08-14 00:01
Modified
2022-04-13 03:04
Summary
Heap-buffer-overflow in yaml_emitter_emit_flow_mapping_key
Details

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

Crash type: Heap-buffer-overflow READ 4
Crash state:
yaml_emitter_emit_flow_mapping_key
yaml_emitter_state_machine
yaml_emitter_emit
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "libyaml"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "acd6f6f014c25e46363e718381e0b35205df2d83"
            }
          ],
          "repo": "https://github.com/yaml/libyaml",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24869\n\n```\nCrash type: Heap-buffer-overflow READ 4\nCrash state:\nyaml_emitter_emit_flow_mapping_key\nyaml_emitter_state_machine\nyaml_emitter_emit\n```\n",
  "id": "OSV-2020-1611",
  "modified": "2022-04-13T03:04:41.717390Z",
  "published": "2020-08-14T00:01:51.615528Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24869"
    }
  ],
  "summary": "Heap-buffer-overflow in yaml_emitter_emit_flow_mapping_key"
}


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.