{"answers":{"affected":"3 open source packages ship an affected version, including triton-vm.","exploited":"There is no known exploitation of GHSA-vjf8-9fx6-mv6x in the wild and no public exploit code.","fix":"Upgrade triton-vm to 4.0.0 or later.","what":"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."},"fix_prompt":"Check this codebase for GHSA-vjf8-9fx6-mv6x and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of GHSA-vjf8-9fx6-mv6x in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- triton-vm (crates.io): affected from 0.42.0-alpha.4; fixed in 4.0.0\n- triton-vm (crates.io): affected from 0.42.0-alpha.4; fixed in 4.0.0\n- triton-vm (crates.io): affected from 0.42.0-alpha.4; fixed in 4.0.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-vjf8-9fx6-mv6x/ (Markdown: https://insights.sbomify.com/GHSA-vjf8-9fx6-mv6x/index.md)","id":"GHSA-vjf8-9fx6-mv6x","markdown":"https://insights.sbomify.com/GHSA-vjf8-9fx6-mv6x/index.md","name":"GHSA-vjf8-9fx6-mv6x","record":{"aliases":["RUSTSEC-2021-0156"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Triton VM library","requires_auth":"none","summary":"Malicious provers can forge memory hashes in Triton VM by bypassing constraints, compromising memory-based commitments in applications using the library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.\n\nAny 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.\n\nThe flaw was corrected in commits `17c7ba0a` and `ef9d9e72` by including the appropriate constraints.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Triton VM Soundness Vulnerability due to Missing Constraint","id":"GHSA-vjf8-9fx6-mv6x","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2021"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["4.0.0"],"introduced":["0.42.0-alpha.4"],"last_affected":[],"package":"triton-vm","purl":null,"source":"GHSA-vjf8-9fx6-mv6x"},{"ecosystem":"crates.io","fixed":["4.0.0"],"introduced":["0.42.0-alpha.4"],"last_affected":[],"package":"triton-vm","purl":"pkg:cargo/triton-vm","source":"GHSA-vjf8-9fx6-mv6x"},{"ecosystem":"crates.io","fixed":["4.0.0"],"introduced":["0.42.0-alpha.4"],"last_affected":[],"package":"triton-vm","purl":"pkg:cargo/triton-vm","source":"RUSTSEC-2021-0156"}],"products":null,"published":"2021-06-11","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Malicious provers can forge memory hashes in Triton VM by bypassing constraints, compromising memory-based commitments in applications using the library.","url":"https://insights.sbomify.com/GHSA-vjf8-9fx6-mv6x/"}