GHSA-gjv3-89hh-9xq2

Source

https://github.com/advisories/GHSA-gjv3-89hh-9xq2

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/06/GHSA-gjv3-89hh-9xq2/GHSA-gjv3-89hh-9xq2.json

JSON Data

https://api.osv.dev/v1/vulns/GHSA-gjv3-89hh-9xq2

Aliases

CVE-2025-52884

Published

2025-06-25T21:27:59Z

Modified

2025-06-25T21:42:11.838495Z

Severity

1.7 (Low) CVSS_V4 - CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U CVSS Calculator

Summary

RISC Zero Ethereum invalid commitment with digest value of zero accepted by Steel.validateCommitment

Details

Impact

Prior to 2.1.1 and 2.2.0, the Steel.validateCommitment Solidity library function will return true for a crafted commitment with a digest value of zero.

This violates the semantics of validateCommitment, as this does not commitment to a block that is in the current chain. Because the digest is zero, it does not correspond to any block and there exist no known openings. As a result, this commitment will never be produced by a correct zkVM guest using Steel. Leveraging this bug to compromise the soundness of an application using Steel would require a separate bug or misuse of the Steel library, which is expected to be used to validate the root of state opening proofs (e.g. having the guest commit to a digest of zero, or failing to check the zkVM proof).

Because this bug does not risk application integrity, correctly written applications are not at risk.

Fix

Please see [#605] for a full description of the bug, and the fix. This fix has been released as part of risc0-ethereum [2.1.1] and [2.2.0].

Recommended actions

Users for the Steel Solidity library versions 2.1.0 or earlier should ensure they are using Steel.validateCommitment in tandem with zkVM proof verification of a Steel program, as shown in the ERC-20 counter example, and [documentation]. This is the correct usage of Steel, and users following this pattern are not at risk, and do not need to take action.

Users not verifying a zkVM proof of a Steel program should update their application to do so, as this is incorrect usage of Steel.

Credit

A thank you to Daniel526 on HackenProof for reporting this issue

Database specific

{
    "nvd_published_at": "2025-06-24T21:15:26Z",
    "cwe_ids": [
        "CWE-159"
    ],
    "severity": "LOW",
    "github_reviewed": true,
    "github_reviewed_at": "2025-06-25T21:27:59Z"
}

References

Affected packages

crates.io / risc0-ethereum-contracts

Package

Name: risc0-ethereum-contracts; View open source insights on deps.dev
Purl: pkg:cargo/risc0-ethereum-contracts

Affected ranges

Type: SEMVER
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

2.1.1