Skip to content
Fencer Intel
low 3.2

GHSA-rjjm-x32p-m3f7 json

gnark's range checker gadget allows wider inputs up to word alignment

published 3y ago modified 2y ago also GO-2023-2333

cvss
3.2
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

gnark provides a gadget in the standard library to allow optimized checking of the bitwidth of the inputs. The gadget works by constructing a fixed lookup table containing all valid entries, partitioning the input and checking that all parts are inside the lookup table. The range checker gadget did not take into account that the highest partition may be less than the width limit, allowing the inputs to be up to 16 bits wider than checked.

Range checking gadget is extensively used in field emulation. Users using any dependant gadget (ECDSA verification, proof recursion etc.) is impacted.

We consider the impact of the vulnerability being low as the number of attacker-modifiable bits is significantly smaller compared to the bit-width of scalar field modulus and it won't be possible to construct inputs which would allow to overflow the scalar field.

### Patches

The issue has been patched in the stable branch of gnark.

Due to low severity of the issue no emergency release will be issued and we follow the existing release plan. Versions v0.9.2 and higher are patched.

### Workarounds

We consider the issue very hard to exploit and do not recommend manual remediation. However, it is possible to perform manual bit decomposition using `std/math/bits` gadget.

### References

Initial issue https://github.com/Consensys/gnark/issues/897

### Acknowledgement

The issue was reported by [@ultrainstinct30](https://github.com/ultrainstinct30).

Patch / fix

  • go github.com/consensys/gnark 0.9.2, 0.9.2-0.20231110170422-f528807119e9

Is GHSA-rjjm-x32p-m3f7 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 3.2 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/consensys/gnark
<0.9.2
<0.9.2-0.20231110170422-f528807119e9
0.9.2
0.9.2-0.20231110170422-f528807119e9

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.