Approved changes feed: RSS · Atom
cpe:2.3:a:hyperledger:ursa:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Hyperledger (619acd7a-fe8a-59d2-9a70-2faf1d5c7fe4) |
|---|---|
| Product | Ursa (d3c37b04-6a21-5fa7-958a-fb8c001a2f56) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:cargo/ursa |
purl2cpe | 2026-06-01 10:12:18.553552 |
pkg:github/hyperledger-archives/ursa |
purl2cpe | 2026-06-01 10:12:18.553555 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-21670 |
vulnerable | 2026-06-08 06:27:36.325698 |
CL-Signatures Revocation Scheme in Ursa has flaws that allow a holder to demonstrate non-revocation of a revoked credential
MEDIUM (6.5)
Ursa is a cryptographic library for use with blockchains. The revocation schema that is part of the Ursa CL-Signatures implementations has a flaw that could impact the privacy guarantees defined by the AnonCreds verifiable credential model, allowing a malicious holder of a revoked credential to generate a valid Non-Revocation Proof for that credential as part of an AnonCreds presentation. A verifier may verify a credential from a holder as being "not revoked" when in fact, the holder's credential has been revoked. Ursa has moved to end-of-life status and no fix is expected.
Published: 2024-01-16T21:44:05.572Z
Updated: 2024-08-01T22:27:35.720Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31021 |
vulnerable | 2026-06-08 05:43:39.996706 |
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 |
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.