CVE-2023-44273 json
gnark-crypto doesn't range check input values during ECDSA and EdDSA signature deserialization
published 2023-09-28 3 y ago modified 2026-06-17 4 mo 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
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
1.05% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
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
References
-
github.com
/Consensys/gnark-crypto/pull/449
web, patch
-
verichains.io
web, product
-
github.com
/Consensys/gnark-crypto/releases
web, release-notes
-
github.com
/Consensys/gnark-crypto/security/advisories/GHSA-fr8m-434r-g3xp
web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-44273
advisory
-
github.com
/Consensys/gnark-crypto
package
-
github.com
/Consensys/gnark-crypto/releases/tag/v0.12.0
web
-
go.dev
/blog/defer-panic-and-recover
web
-
github.com
/advisories/GHSA-9xfq-8j3r-xp5g
advisory, web
Sources
- CVE List CVE-2023-44273
- GitHub Advisory GHSA-fr8m-434r-g3xp
- GitHub Advisory GHSA-9xfq-8j3r-xp5g
- NVD CVE-2023-44273
- OSV GO-2023-2096
- OSV GO-2025-4027
Fencer Vulns 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.