wasmtime is vulnerable to Type Confusion
59
CVE Score
Medium
Type Confusion
Wasmtime's validation of WebAssembly components does not correctly check tag imports on an instantiated core module, so a component can import a tag whose type is a mismatched subtype of the module's declared tag, which the WebAssembly specification forbids. A guest can use that gap to mistype the payload of an exception object, and the garbage collector then processes that payload as the declared type, corrupting the GC heap. The bug only affects guests that use the WebAssembly exceptions proposal, which is on by default, and a corrupted GC heap can cause the host to panic during unrelated operations. The fix rejects components whose tag imports use an incompatible subtype during validation.
Upgrade the wasmtime library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you run untrusted WebAssembly components with the WebAssembly exceptions proposal enabled.
47.0.0 - 48.0.3
Fixed in 48.0.449.0.0 - 49.0.1
Fixed in 49.0.2wasmtime is vulnerable to Type Confusion in versions 47.0.0 - 48.0.3 and 49.0.0 - 49.0.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.