osv-2022-478
Vulnerability from osv_ossfuzz
Published
2022-06-14 00:01
Modified
2023-10-09 14:11
Summary
Segv on unknown address
Details

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

Crash type: Segv on unknown address Crash state: NULL


{
  "affected": [
    {
      "database_specific": {
        "introduced_range": "cbce0cbffed81b8ae57e8f1e9108af6d62ef2bd1:fd094fe2fcd55d1d0f21c20fe664f6cfd896f461"
      },
      "ecosystem_specific": {
        "severity": null
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "libzmq",
        "purl": "pkg:generic/libzmq"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "e708623c12e3179c5aebcc5005a56e0b44ac7ecf"
            }
          ],
          "repo": "https://github.com/zeromq/libzmq.git",
          "type": "GIT"
        }
      ],
      "versions": [
        "v4.3.3",
        "v4.3.4",
        "v4.3.5"
      ]
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48005\n\n```\nCrash type: Segv on unknown address\nCrash state:\nNULL```\n",
  "id": "OSV-2022-478",
  "modified": "2023-10-09T14:11:11.908246Z",
  "published": "2022-06-14T00:01:10.335839Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48005"
    }
  ],
  "schema_version": "1.2.0",
  "summary": "Segv on unknown address"
}


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…