CVE-2022-31021 json
Unlinkability broken in ursa when verifiers use malicious keys
published 2024-01-16 2 y ago modified 2026-06-17 4 mo ago also GHSA-2q6j-gqc4-4gw3 , EUVD-2024-0224
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
Ursa is a cryptographic library for use with blockchains. A weakness in the Hyperledger AnonCreds specification that is not mitigated in the Ursa and AnonCreds implementations is that the Issuer does not publish a key correctness proof demonstrating that a generated private key is sufficient to meet the unlinkability guarantees of AnonCreds. The Ursa and AnonCreds CL-Signatures implementations always generate a sufficient private key. A malicious issuer could in theory create a custom CL Signature implementation (derived from the Ursa or AnonCreds CL-Signatures implementations) that uses weakened private keys such that presentations from holders could be shared by verifiers to the issuer who could determine the holder to which the credential was issued. This vulnerability could impact holders of AnonCreds credentials implemented using the CL-signature scheme in the Ursa and AnonCreds implementations of CL Signatures. The ursa project has has moved to end-of-life status and no fix is expected.
Patch / fix
- hyperledger ursa 0.3
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- brics.dk https://www.brics.dk/RS/98/29/BRICS-RS-98-29.pdf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | anoncreds-clsignatures | all versions |
no fix listed |
| crates.io | ursa | <=0.3.7 |
no fix listed |
Affected products
- hyperledger ursa
Classification
- Weakness
-
- CWE-829 Inclusion of Functionality from Untrusted Control Sphere
References
-
brics.dk
/RS/98/29/BRICS-RS-98-29.pdf
web, exploit, third-party-advisory
-
github.com
/hyperledger/ursa/security/advisories/GHSA-2q6j-gqc4-4gw3
web, vendor-advisory
-
github.com
/hyperledger-archives/ursa/security/advisories/GHSA-2q6j-gqc4-4gw3
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-31021
advisory
-
github.com
/hyperledger-archives/ursa
package
Sources
- CVE List CVE-2022-31021
- GitHub Advisory GHSA-2q6j-gqc4-4gw3
- NVD CVE-2022-31021
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.