{"answers":{"affected":"2 open source packages ship an affected version, including risc0-zkvm.","exploited":"There is no known exploitation of GHSA-5xgj-pmjj-gw49 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-5xgj-pmjj-gw49 yet. Limit exposure of the affected software until one is available.","what":"GHSA-5xgj-pmjj-gw49 is a vulnerability in risc0-zkvm, published on 15 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-5xgj-pmjj-gw49 and fix it if it is affected.\n\nWhat it is: GHSA-5xgj-pmjj-gw49 is a vulnerability in risc0-zkvm, published on 15 Jul 2024. 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-5xgj-pmjj-gw49 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- risc0-zkvm (crates.io): affected all versions up to 1.0.2; no fix listed\n- risc0-zkvm (crates.io): affected all versions up to 1.0.2; no fix listed\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-5xgj-pmjj-gw49/ (Markdown: https://insights.sbomify.com/GHSA-5xgj-pmjj-gw49/index.md)","id":"GHSA-5xgj-pmjj-gw49","markdown":"https://insights.sbomify.com/GHSA-5xgj-pmjj-gw49/index.md","name":"GHSA-5xgj-pmjj-gw49","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RISC Zero zkVM","requires_auth":"none","summary":"RISC Zero zkVM fails to provide provable zero-knowledge guarantees, potentially leaking execution details in privacy-critical applications.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"RISC Zero zkVM was designed from its inception to provide three main guarantees:\n1. *Computational integrity*: that a given software program executed correctly.\n2. *Succinctness*: that the proof of execution does not grow in relation to the program being executed.\n3. *Zero Knowledge*: that details of the program execution are not visible within the proof of program execution.\n\nUlrich Habock and Al Kindi have released [new research] that indicates that several STARK implementations -including our RISC Zero zkVM- do not meet the requirements to assert the specific property of zero knowledge provably. \n\nWhile a vast majority of real-world applications that leverage RISC Zero zkVM or similar systems depend primarily on computational integrity and succinctness, a subset of applications critically depend on the privacy guarantees provided by zero-knowledge; and for those use cases, users are cautioned to understand the research and make informed decisions based on the risks outlined in using an impacted system.\n\nAlthough the maintainers are not aware of any attacks that can take advantage of this potential weakness, they are working to proactively address this discovery as quickly as possible. \n\n[new research]: https://eprint.iacr.org/2024/1037","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":false,"headline":"RISC Zero zkVM notes on zero-knowledge","id":"GHSA-5xgj-pmjj-gw49","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.0.2"],"package":"risc0-zkvm","purl":null,"source":"GHSA-5xgj-pmjj-gw49"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.0.2"],"package":"risc0-zkvm","purl":"pkg:cargo/risc0-zkvm","source":"GHSA-5xgj-pmjj-gw49"}],"products":null,"published":"2024-07-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"RISC Zero zkVM fails to provide provable zero-knowledge guarantees, potentially leaking execution details in privacy-critical applications.","url":"https://insights.sbomify.com/GHSA-5xgj-pmjj-gw49/"}