Advisory

GHSA-jf2r-x3j4-23m7

Also known as: CVE-2025-46723

Summary

OpenVM allows the byte decomposition of pc in AUIPC chip to overflow

Details

The fix to https://cantina.xyz/code/c486d600-bed0-4fc6-aed1-de759fd29fa2/findings/21 has a typo that still results in the highest limb of pc being range checked to 8-bits instead of 6-bits.

In the AIR, we do https://github.com/openvm-org/openvm/blob/0f94c8a3dfa7536c1231465d1bdee5fc607a5993/extensions/rv32im/circuit/src/auipc/core.rs#L135

        for (i, limb) in pc_limbs.iter().skip(1).enumerate() {
            if i == pc_limbs.len() - 1 {

It should be

        for (i, limb) in pc_limbs.iter().enumerate().skip(1) {

Right now the if statement is never triggered because the enumeration gives i=0,1,2 when we instead want i=1,2,3. What this means is that pc_limbs[3] is range checked to 8-bits instead of 6-bits.

This leads to a vulnerability where the pc_limbs decomposition differs from the true pc, which means a malicious prover can make the destination register take a different value than the AUIPC instruction dictates, by making the decomposition overflow the BabyBear field.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-05-05 19:57 UTC
Modified
2025-05-05 20:42 UTC

Affected packages and fixes

openvm

crates.io · All systems

Affected

  • introduced 1.0.0, fixed 1.1.0 (semver)

Fixed versions

1.1.0

Fix

  • Fixed version 1.1.0
    cargo update -p openvm --precise 1.1.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences