CVE-2022-28990: Buffer overflow in wasm3

pywasm3 Updated 02 Oct 2025

Summary

21/05/2022
No i
High
7.8

CVE-2022-28990: Buffer overflow in wasm3. Affects pywasm3 versions < 0.5.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package under scrutiny is wasm3, specifically version 0.5.0. wasm3 is a WebAssembly interpreter that allows executing WebAssembly modules in various environments. It provides a lightweight and efficient solution for running WebAssembly code. However, version 0.5.0 of wasm3 has been found to contain a buffer overflow vulnerability. This vulnerability can be exploited via the component /wabt/bin/poc.wasm, leading to a heap overflow.

Vulnerability Detail

The buffer overflow vulnerability in wasm3 (version 0.5.0) is a heap overflow issue. It occurs when processing the /wabt/bin/poc.wasm component. An attacker can exploit this vulnerability to overwrite adjacent memory locations, potentially leading to arbitrary code execution or a denial of service (DoS) attack. The severity of this vulnerability is rated as HIGH with a CVSS score of 7.8. The Common Weakness Enumeration (CWE) ID associated with this vulnerability is CWE-787.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

At the moment, there is no known workaround for this vulnerability. It is crucial to update to a patched version of wasm3 as soon as possible.

Conclusion

In conclusion, wasm3 version 0.5.0 has been found to contain a buffer overflow vulnerability that can be exploited via the /wabt/bin/poc.wasm component. It is crucial for users of wasm3 to update to a patched version to mitigate the risks associated with this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for pywasm3 →

Share this vulnerability

FAQ

wasm3 is a WebAssembly interpreter that allows executing WebAssembly modules in various environments. It provides a lightweight and efficient solution for running WebAssembly code.

The buffer overflow vulnerability in wasm3 can potentially lead to arbitrary code execution or a denial of service (DoS) attack. It is important to update to a patched version to mitigate these risks.

The severity of this vulnerability is rated as HIGH with a CVSS score of 7.8.

At the moment, there is no known workaround for this vulnerability. It is crucial to update to a patched version of wasm3 as soon as possible.

To fix this vulnerability, it is recommended to update the wasm3 package to a version that includes a patch for the buffer overflow issue. Check the official repository or package manager for the latest version and update your installation.

Related vulnerabilities

Recent vulnerabilities recorded for pywasm3.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback