PYSEC-2022-43187

Vulnerability from pysec - Published: 2022-10-28 21:15 - Updated: 2026-05-20 09:19
VLAI?
Details

wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector>::size() at /bits/stl_vector.h.

Impacted products
Name purl
wabt pkg:pypi/wabt
Aliases

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "wabt",
        "purl": "pkg:pypi/wabt"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {}
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1",
        "0.1.1",
        "0.1.2"
      ]
    }
  ],
  "aliases": [
    "CVE-2022-43281"
  ],
  "details": "wasm-interp v1.0.29 was discovered to contain a heap overflow via the component std::vector\u003cwabt::Type, std::allocator\u003cwabt::Type\u003e\u003e::size() at /bits/stl_vector.h.",
  "id": "PYSEC-2022-43187",
  "modified": "2026-05-20T09:19:22.350833Z",
  "published": "2022-10-28T21:15:09.883Z",
  "references": [
    {
      "type": "FIX",
      "url": "https://github.com/WebAssembly/wabt/issues/1981"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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…