Proof integrity bypass via AUIPC limb overflow
Published May 2, 2025 · Updated May 6, 2025
Improper range checking in OpenVM 1.0.0 allows remote attackers to produce an AUIPC result that violates the proved instruction. The AUIPC AIR enumerates after skipping the first program-counter limb, so the final limb receives an 8-bit rather than 6-bit range check and can overflow the BabyBear field. Exploitation requires a malicious prover to submit the overflowing decomposition, which corrupts the destination-register result and undermines proof integrity.
Summary
What happened
Improper range checking in OpenVM 1.0.0 allows remote attackers to produce an AUIPC result that violates the proved instruction. The AUIPC AIR enumerates after skipping the first program-counter limb, so the final limb receives an 8-bit rather than 6-bit range check and can overflow the BabyBear field. Exploitation requires a malicious prover to submit the overflowing decomposition, which corrupts the destination-register result and undermines proof integrity.
The record
- CVE
- CVE-2025-46723
- Published
- May 2, 2025
- Updated
- May 6, 2025
- Vendor
- OpenVM
- Product
- OpenVM
- Classifications
- CWE-131, T1565
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- May 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 1.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo