Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
A use-after-free vulnerability has been discovered in the linear memory implementation of Wasmi. This issue can be triggered by a WebAssembly module under certain memory growth conditions, potentially leading to memory corruption, information disclosure, or code execution. Impact - Confidentiality: High – attacker-controlled memory reads possible. - Integrity: High – memory corruption may allow arbitrary writes. - Availability: High – interpreter crashes possible. Affected Versions Wasmi v0.41.0 through Wasmi v1.0.0. Workarounds - Upgrade to the latest patched version of Wasmi. - Consider limiting the maximum linear memory sizes where feasible. Credits This vulnerability was discovered by Robert T. Morris (RTM).
Recommended action: Upgrade to 1.0.1, 0.51.3, 0.47.1 or 0.41.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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: <PR Special thanks Special thanks to Stellar Development Foundation for reporting this security vulnerability.
Recommended action: Upgrade to 0.31.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.