The Triton VM soundness vulnerability allows attackers to forge memory hashes due to missing constraints. This flaw was corrected in commits 17c7c0a and ef9d9e72 by including the appropriate constraints. The vulnerability affects applications using instruction sponge_absorb_mem to hash memory data, allowing malicious provers to substitute arbitrary data instead of actual memory contents. The Triton VM fails to verify that hashed values come from the claimed memory location, enabling attackers to create a proof for a forged hash that doesn't correspond to the actual memory. This breaks the security of memory-based commitments. The affected packages include triton-vm versions 0.42.0-alpha.4 through less than 4.0.0, with version 4.0.0 being patched. The vulnerability has a medium severity level and is categorized as CWE-345. It was reported in the GitHub Security Advisory GHSA-vjf8-9fx6-mv6x, which provides further information on the affected packages and references.
We recommend you to update Triton VM to version 4.0.0.[/subscribe_to_unlock_form]
The Triton VM soundness vulnerability allows attackers to forge memory hashes due to missing constraints. This flaw was corrected in commits 17c7c0a and ef9d9e72 by including the appropriate constraints. The vulnerability affects applications using instruction sponge_absorb_mem to hash memory data, allowing malicious provers to substitute arbitrary data instead of actual memory contents. The Triton VM fails to verify that hashed values come from the claimed memory location, enabling attackers to create a proof for a forged hash that doesn't correspond to the actual memory. This breaks the security of memory-based commitments. The affected packages include triton-vm versions 0.42.0-alpha.4 through less than 4.0.0, with version 4.0.0 being patched. The vulnerability has a medium severity level and is categorized as CWE-345. It was reported in the GitHub Security Advisory GHSA-vjf8-9fx6-mv6x, which provides further information on the affected packages and references.
We recommend you to update Triton VM to version 4.0.0.[emaillocker id="1283"]
The following reports contain further technical details:
[/emaillocker]