osv-2022-283
Vulnerability from osv_ossfuzz
Published
2022-03-26 00:01
Modified
2022-03-26 00:01
Summary
Heap-buffer-overflow in epassNUMBER_hook_path
Details

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

Crash type: Heap-buffer-overflow READ 1
Crash state:
epassNUMBER_hook_path
epassNUMBER_hook_file
epassNUMBER_create_file

{
  "affected": [
    {
      "ecosystem_specific": {
        "severity": "MEDIUM"
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "opensc",
        "purl": "pkg:generic/opensc"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "bec4f63c5b8308d7fdca842c5c0b62c3491d106a"
            },
            {
              "fixed": "da37a0d5ece632080351c529ac87f00495eddbfa"
            }
          ],
          "repo": "https://github.com/OpenSC/OpenSC",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46006\n\n```\nCrash type: Heap-buffer-overflow READ 1\nCrash state:\nepassNUMBER_hook_path\nepassNUMBER_hook_file\nepassNUMBER_create_file\n```\n",
  "id": "OSV-2022-283",
  "modified": "2022-03-26T00:01:45.914434Z",
  "published": "2022-03-26T00:01:45.914197Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46006"
    }
  ],
  "schema_version": "1.2.0",
  "summary": "Heap-buffer-overflow in epassNUMBER_hook_path"
}


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…