osv-2020-2000
Vulnerability from osv_ossfuzz
Published
2020-10-09 00:00
Modified
2022-04-13 03:04
Summary
Heap-buffer-overflow in sctp_process_init
Details

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

Crash type: Heap-buffer-overflow WRITE 1
Crash state:
sctp_process_init
sctp_process_cookie_existing
sctp_handle_cookie_echo

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "HIGH"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "usrsctp"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "cfa8402646237a1fb78f0b8bd65be4a1afd4bee6"
            },
            {
              "fixed": "f4925bd5ebb2db38263eef0ec816bf393293cf9c"
            }
          ],
          "repo": "https://github.com/sctplab/usrsctp",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26197\n\n```\nCrash type: Heap-buffer-overflow WRITE 1\nCrash state:\nsctp_process_init\nsctp_process_cookie_existing\nsctp_handle_cookie_echo\n```\n",
  "id": "OSV-2020-2000",
  "modified": "2022-04-13T03:04:42.608737Z",
  "published": "2020-10-09T00:00:08.332453Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26197"
    }
  ],
  "summary": "Heap-buffer-overflow in sctp_process_init"
}


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…