OpenVM is a performant and modular zkVM framework built for customization and extensibility

Why it is Yellow

• CVSS 8.7 high
• Remotely exploitable without logging in

References

• https://github.com/openvm-org/openvm/blob/v2.0.0-alpha/crates/vm/src/system/memory/merkle/air.rs
• https://github.com/openvm-org/openvm/blob/v2.0.0-beta.2/crates/vm/src/system/memory/merkle/air.rs
• https://github.com/openvm-org/openvm/blob/v2.1.0-dev.0/crates/vm/src/system/memory/merkle/air.rs
• https://github.com/openvm-org/openvm/commit/bb123f6073691bd2b794171c594264c77e45c376
• https://github.com/openvm-org/openvm/pull/148
• https://github.com/openvm-org/openvm/releases/tag/v1.7.0
• https://github.com/openvm-org/openvm/releases/tag/v2.0.0-rc.3
• https://github.com/openvm-org/openvm/releases/tag/v2.1.0-preview
• https://github.com/openvm-org/openvm/security/advisories/GHSA-396x-v8w4-9x82

Original description

OpenVM is a performant and modular zkVM framework built for customization and extensibility. Before 1.7.0 in the 1.x line and in affected 2.0 and 2.1 prereleases, `MemoryMerkleAir` does not forbid Merkle expansion rows at `parent_height` = 0 or below while `expand_direction` != 0. A malicious prover can fabricate a subtree below a memory leaf and swap digests inside that subtree to change the committed memory root without a corresponding memory operation. The fraudulent rows still balance against the Merkle and compression buses and require no memory-bus operation for the changed leaf. Because the memory Merkle root binds VM memory state across continuation segment boundaries, this affects the soundness of OpenVM proofs using persistent memory. This issue is fixed in versions 1.7.0, 2.0.0-rc.3 and 2.1.0-preview.