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.
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.
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.
Ensure no more than 128 parameters can be pass in a call from the host to a Wasm function.
Patch PR: <PR>
Special thanks to Stellar Development Foundation for reporting this security vulnerability.
| Score | Percentile |
|---|---|
| 0.31% | 53.86% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 7.3 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-75jp-vq8x-h4cq ↗ |
| CVE | CVE-2024-28123 ↗ |
| CWE id | Name |
|---|---|
| CWE-787 | Out-of-bounds Write |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| rust | wasmi | >= 0.15.0, <= 0.31.0 | 0.31.1 | — |