CVE-2022-28966 Memory corruption in n/a
A heap-based buffer overflow in Wasm3 allows attackers to execute arbitrary code or cause denial of service via crafted WebAssembly modules.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2022-28966?
CVE-2022-28966 is a medium-severity memory corruption vulnerability in n/a, published on 16 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
Wasm3 0.5.0 has a heap-based buffer overflow in NewCodePage in m3_code.c (called indirectly from Compile_BranchTable in m3_compile.c).
Weakness: CWE-787
Which versions are affected by CVE-2022-28966?
It affects 1 product.
Products include Wasm3 Project Wasm3.
How do I fix CVE-2022-28966?
No fix has been published for CVE-2022-28966 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2022-28966 being exploited?
There is no known exploitation of CVE-2022-28966 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2024-34249 pywasm3 contains a heap buffer overflow which leads to segmentation fault
- CVE-2024-27528 pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution
- CVE-2024-27529 wasm3 uncontrolled memory allocation vulnerability
- CVE-2024-27530 pywasm3 contains a Use-After-Free in ForEachModule
- CVE-2022-28990 Buffer overflow in wasm3
Sources
Also known as GHSA-4jf4-7v2f-64pc.