Search
Search Results (8 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2025-3122 | 1 Webassembly | 2 Wabt, Webassembly Binary Toolkit | 2025-09-23 | 3.1 Low |
| A vulnerability classified as problematic was found in WebAssembly wabt 1.0.36. Affected by this vulnerability is the function BinaryReaderInterp::BeginFunctionBody of the file src/interp/binary-reader-interp.cc. The manipulation leads to null pointer dereference. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. | ||||
| CVE-2023-27115 | 1 Webassembly | 1 Webassembly | 2025-02-28 | 5.5 Medium |
| WebAssembly v1.0.29 was discovered to contain a segmentation fault via the component wabt::cat_compute_size. | ||||
| CVE-2023-27116 | 1 Webassembly | 1 Webassembly | 2025-02-28 | 5.5 Medium |
| WebAssembly v1.0.29 discovered to contain an abort in CWriter::MangleType. | ||||
| CVE-2023-27117 | 1 Webassembly | 1 Webassembly | 2025-02-28 | 7.8 High |
| WebAssembly v1.0.29 was discovered to contain a heap overflow via the component component wabt::Node::operator. | ||||
| CVE-2023-31670 | 1 Webassembly | 1 Webassembly Binary Toolkit | 2025-01-31 | 7.5 High |
| An issue in wasm2c 1.0.32, wasm2wat 1.0.32, wasm-decompile 1.0.32, and wasm-validate 1.0.32 allows attackers to cause a Denial of Service (DoS) via running a crafted binary. | ||||
| CVE-2023-31669 | 1 Webassembly | 1 Webassembly Binary Toolkit | 2025-01-31 | 5.5 Medium |
| WebAssembly wat2wasm v1.0.32 allows attackers to cause a libc++abi.dylib crash by putting '@' before a quote ("). | ||||
| CVE-2023-46332 | 1 Webassembly | 1 Webassembly Binary Toolkit | 2024-11-21 | 5.5 Medium |
| WebAssembly wabt 1.0.33 contains an Out-of-Bound Memory Write in DataSegment::Drop(), which lead to segmentation fault. | ||||
| CVE-2023-46331 | 1 Webassembly | 1 Webassembly Binary Toolkit | 2024-11-21 | 5.5 Medium |
| WebAssembly wabt 1.0.33 has an Out-of-Bound Memory Read in in DataSegment::IsValidRange(), which lead to segmentation fault. | ||||
Page 1 of 1.