Skip to content

Wasmi Out-of-bounds Write for host to Wasm calls with more than 128 Parameters

Critical severity GitHub Reviewed Published Mar 7, 2024 in wasmi-labs/wasmi • Updated Mar 7, 2024

Package

cargo wasmi (Rust)

Affected versions

>= 0.15.0, <= 0.31.0

Patched versions

0.31.1

Description

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

@Robbepop Robbepop published to wasmi-labs/wasmi Mar 7, 2024
Published to the GitHub Advisory Database Mar 7, 2024
Reviewed Mar 7, 2024
Last updated Mar 7, 2024

Severity

Critical

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-28123

GHSA ID

GHSA-75jp-vq8x-h4cq

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.