Summary
In the WASMI Interpreter, an Out-of-bounds Buffer Write will arise arise if the host calls or resumes a Wasm function with more parameters than the default limit (128), as it will surpass the stack value. This doesn’t affect calls from Wasm to Wasm, only from host to Wasm.
Impact
After conducting an analysis of the dependent Polkadot systems of wasmi: Pallet Contracts, Parity Signer, and Smoldot, we have found that none on those systems have been affected by the issue as they are calling host to Wasm function with a small limited amount of parameters always.
Mitigations
If you are using wasmi betwen version 0.15.0 and 0.31.0, please update it to the 0.31.1 patch release that we just published.
Workarounds
Ensure no more than 128 parameters can be pass in a call from the host to a Wasm function.
References
Patch PR:
Special thanks
Special thanks to Stellar Development Foundation for reporting this security vulnerability.
References
Summary
In the WASMI Interpreter, an Out-of-bounds Buffer Write will arise arise if the host calls or resumes a Wasm function with more parameters than the default limit (128), as it will surpass the stack value. This doesn’t affect calls from Wasm to Wasm, only from host to Wasm.
Impact
After conducting an analysis of the dependent Polkadot systems of
wasmi: Pallet Contracts, Parity Signer, and Smoldot, we have found that none on those systems have been affected by the issue as they are calling host to Wasm function with a small limited amount of parameters always.Mitigations
If you are using
wasmibetwen version 0.15.0 and 0.31.0, please update it to the 0.31.1 patch release that we just published.Workarounds
Ensure no more than 128 parameters can be pass in a call from the host to a Wasm function.
References
Patch PR:
Special thanks
Special thanks to Stellar Development Foundation for reporting this security vulnerability.
References