Skip to content
Fencer Intel
critical 9.8

CVE-2023-44273 json

gnark-crypto doesn't range check input values during ECDSA and EdDSA signature deserialization

published 3y ago modified 4mo ago also GHSA-9xfq-8j3r-xp5g , GHSA-fr8m-434r-g3xp , GO-2023-2096 , GO-2025-4027 , EUVD-2023-2485

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

Consensys gnark-crypto through 0.11.2 allows Signature Malleability. This occurs because deserialisation of EdDSA and ECDSA signatures does not ensure that the data is in a certain interval.

Patch / fix

  • go github.com/consensys/gnark-crypto 0.12.0
  • consensys gnark-crypto 0.12.0

Is CVE-2023-44273 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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

1.06% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/consensys/gnark-crypto
<0.12.0
0.12.0

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
  • CWE-347 Improper Verification of Cryptographic Signature

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.