Medium severity · published Apr 2, 2025
CVE-2025-3122
WebAssembly wabt binary-reader-interp.cc BeginFunctionBody null pointer dereference
5.3
CVSS
0.6%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 49% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
WA
wabt · WebAssembly
1.0.36 · source: vendor
WB
Webassembly Binary Toolkit · Webassembly
1.0.36 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-3122
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-3122
Exploit
https://github.com/WebAssembly/wabt/issues/2565
Exploit
https://github.com/WebAssembly/wabt/issues/2565#issue-2927572319
Permissions Required
https://vuldb.com/?ctiid.303013
Third Party Advisory
https://vuldb.com/?id.303013
Third Party Advisory
https://vuldb.com/?submit.525091
More from wabt
8.8
CVE-2025-2368
WebAssembly wabt Malformed File binary-reader-interp.cc OnExport heap-based overflow
7.8
CVE-2025-15412
WebAssembly wabt wasm-decompile VarName out-of-bounds
7.8
CVE-2025-15411
WebAssembly wabt wasm-decompile InsertNode memory corruption
7.1
CVE-2026-90648
wasm2c in WebAssembly wabt through 1.0.41 allows sandbox escape in some situations that primarily involve 32-bit platforms, aka a "table flip" attack
7.1
CVE-2022-43280
wasm-interp v1.0.29 was discovered to contain an out-of-bounds read via the component OnReturnCallExpr->GetReturnCallDropKeepCount