# GHSA-vjf8-9fx6-mv6x: Triton VM Soundness Vulnerability due to Missing Constraint

> Malicious provers can forge memory hashes in Triton VM by bypassing constraints, compromising memory-based commitments in applications using the library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jun 2021
- **Also known as:** RUSTSEC-2021-0156

## What is GHSA-vjf8-9fx6-mv6x?

GHSA-vjf8-9fx6-mv6x is a vulnerability in triton-vm, published on 11 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The instruction `sponge_absorb_mem` Triton VM fails to verify that hashed values come from the claimed memory location. Malicious provers can substitute arbitrary data instead of actual memory contents.

Any application using instruction `sponge_absorb_mem` to hash memory data can be given a proof for a forged hash that doesn't correspond to the actual memory. This breaks the security of memory-based commitments.

The flaw was corrected in commits `17c7ba0a` and `ef9d9e72` by including the appropriate constraints.

## Which versions are affected by GHSA-vjf8-9fx6-mv6x?

3 open source packages ship an affected version, including triton-vm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `triton-vm` | crates.io | From 0.42.0-alpha.4 | 4.0.0 |
| `triton-vm` | crates.io | From 0.42.0-alpha.4 | 4.0.0 |
| `triton-vm` | crates.io | From 0.42.0-alpha.4 | 4.0.0 |

## How do I fix GHSA-vjf8-9fx6-mv6x?

Upgrade triton-vm to 4.0.0 or later.

## Is GHSA-vjf8-9fx6-mv6x being exploited?

There is no known exploitation of GHSA-vjf8-9fx6-mv6x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-vjf8-9fx6-mv6x and fix it if it is affected.

What it is: GHSA-vjf8-9fx6-mv6x is a vulnerability in triton-vm, published on 11 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-vjf8-9fx6-mv6x in the wild and no public exploit code.

Affected packages and fixed versions:
- triton-vm (crates.io): affected from 0.42.0-alpha.4; fixed in 4.0.0
- triton-vm (crates.io): affected from 0.42.0-alpha.4; fixed in 4.0.0
- triton-vm (crates.io): affected from 0.42.0-alpha.4; fixed in 4.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-vjf8-9fx6-mv6x/ (Markdown: https://insights.sbomify.com/GHSA-vjf8-9fx6-mv6x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-vjf8-9fx6-mv6x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-vjf8-9fx6-mv6x/
Summaries are generated and may contain mistakes; the official description above is the record.