CVE-2022-31021

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-31021
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-31021.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-31021
Aliases
Published
2024-01-16T22:15:37Z
Modified
2024-09-03T04:15:51.546988Z
Severity
  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CVSS Calculator
Summary
[none]
Details

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.

References

Affected packages

Git / github.com/hyperledger-archives/ursa

Affected ranges

Type
GIT
Repo
https://github.com/hyperledger-archives/ursa
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

v0.*

v0.1.0
v0.1.1
v0.2.0