Approved changes feed: RSS · Atom

cpe:2.3:a:hyperledger:ursa:*:*:*:*:*:rust:*:*

part: a version: * update: *

VendorHyperledger (619acd7a-fe8a-59d2-9a70-2faf1d5c7fe4)
ProductUrsa (d3c37b04-6a21-5fa7-958a-fb8c001a2f56)
Edition*
Language*
Software edition*
Target softwarerust
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:cargo/ursa purl2cpe 2026-06-01 10:12:18.555570
pkg:github/hyperledger-archives/ursa purl2cpe 2026-06-01 10:12:18.555571

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-31021 vulnerable 2026-06-08 05:43:39.997431 Unlinkability broken in ursa when verifiers use malicious keys
LOW (3.3)
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.
Published: 2024-01-16T21:35:31.306Z
Updated: 2025-06-02T15:08:17.415Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.