CVE-2022-44874 Memory corruption in n/a
A segmentation fault in the wasm3 WebAssembly runtime allows attackers to cause a denial of service via crafted input.
- 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-44874?
CVE-2022-44874 is a medium-severity memory corruption vulnerability in n/a, published on 13 Dec 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 commit 7890a2097569fde845881e0b352d813573e371f9 was discovered to contain a segmentation fault via the component op_CallIndirect at /m3_exec.h.
Weakness: CWE-787
Which versions are affected by CVE-2022-44874?
It affects 1 product.
Products include Wasm3 Project Wasm3.
How do I fix CVE-2022-44874?
No fix has been published for CVE-2022-44874 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-44874 being exploited?
There is no known exploitation of CVE-2022-44874 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-p3wp-rmx9-wmxp.