{"answers":{"affected":"2 open source packages ship an affected version, including mithril-client.","exploited":"There is no known exploitation of GHSA-qv97-5qr8-2266 in the wild and no public exploit code.","fix":"Upgrade mithril-client to 0.12.2 or later.","what":"GHSA-qv97-5qr8-2266 is a vulnerability in mithril-client, published on 7 May 2025."},"fix_prompt":"Check this codebase for GHSA-qv97-5qr8-2266 and fix it if it is affected.\n\nWhat it is: GHSA-qv97-5qr8-2266 is a vulnerability in mithril-client, published on 7 May 2025. \nExploitation: There is no known exploitation of GHSA-qv97-5qr8-2266 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mithril-client (crates.io): affected all versions; fixed in 0.12.2\n- mithril-client (crates.io): affected all versions; fixed in 0.12.2\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-qv97-5qr8-2266/ (Markdown: https://insights.sbomify.com/GHSA-qv97-5qr8-2266/index.md)","id":"GHSA-qv97-5qr8-2266","markdown":"https://insights.sbomify.com/GHSA-qv97-5qr8-2266/index.md","name":"GHSA-qv97-5qr8-2266","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\n#### Mithril certification of Cardano database\n\nThe Mithril network provides certification for snapshots of the Cardano database, enabling users to quickly bootstrap a Cardano node without relying on the slower peer-to-peer synchronization process.\n\nTo generate a multi-signature, a minimum threshold of Cardano stake registered in the protocol must agree on signing the same message. In this context, a digest is computed from the internal files of the Cardano node's database. However, this mechanism has certain limitations. Specifically, some files are not identically generated across all Cardano nodes, and there is no API to provide consistent snapshots at a specific beacon on the Cardano chain:\n\n- All immutable files, except the last one (which is still being created), are used to compute the message\n- The last immutable file is excluded from the signature\n- The ledger state files are also excluded from the signature.\n\n#### Cardano node startup sequence\n\nA Cardano node can only perform a fast bootstrap if a pre-computed ledger state is loaded into its database; otherwise, a full re-computation is required, which is time-consuming. During the startup phase with a pre-computed ledger state, the node performs structural verification of the ledger state and lightweight conformity checks which may not be enough to systematically detect invalid ledger state.\n\n#### Attack scenarios\n\nInconsistencies could be introduced into a tampered ledger state distributed through Mithril snapshots, either by an unknown source or by a compromised IOG-operated aggregator. These inconsistencies would not be immediately detected by Cardano nodes started with such snapshots, potentially enabling long-range attacks that might not be corrected by honest nodes, even if they sync from genesis.\n\nCurrently, a Mithril network has only one aggregator, which serves snapshots from a secure cloud location operated by IOG and is therefore assumed to be trustworthy. In the future, as Mithril networks become more decentralized, multiple aggregators will operate independently. This increased decentralization could raise the risk of a malicious aggregator distributing a tampered ledger state.\n\n### Patches\n\nAs a mitigation, the Mithril aggregator now signs the ledger state snapshot and the latest immutable file using an IOG-owned key, and the client library and CLI validate the signature of these files upon download.\n\n- The **Mithril client library** has been fixed with version `0.12.2`, **previous versions must not be used anymore**.\n- The **Mithril client CLI** has been fixed with version `0.12.1`, **previous versions must not be used anymore**.\n- The **Mithril aggregator** has been fixed with version `0.7.44`, **previous versions must not be used anymore**.\n\n### References\n\n- _Mithril protocol in depth_: https://mithril.network/doc/next/mithril/mithril-protocol/protocol\n- _Bootstrap a Cardano node_: https://mithril.network/doc/manual/getting-started/bootstrap-cardano-node\n- _Mithril certification of the Cardano node database_: https://mithril.network/doc/mithril/advanced/mithril-certification/cardano-node-database","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":"Mithril snapshots for Cardano database could be compromised by an adversary","id":"GHSA-qv97-5qr8-2266","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.12.2"],"introduced":["0"],"last_affected":[],"package":"mithril-client","purl":null,"source":"GHSA-qv97-5qr8-2266"},{"ecosystem":"crates.io","fixed":["0.12.2"],"introduced":["0"],"last_affected":[],"package":"mithril-client","purl":"pkg:cargo/mithril-client","source":"GHSA-qv97-5qr8-2266"}],"products":null,"published":"2025-05-07","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":null,"url":"https://insights.sbomify.com/GHSA-qv97-5qr8-2266/"}