CVE-2024-21670: CL-Signatures Revocation Scheme in Ursa has flaws that allow a holder to demonstrate non-revocation of a revoked credential

CVE-2024-21670 · Severity: low · CVSS 3.1 · Published 2024-01-16

CL-Signatures Revocation Scheme in Ursa has flaws that allow a holder to demonstrate non-revocation of a revoked credential

Technologies: anoncreds-clsignatures (crates.io), ursa (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2024-21670 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-21670 being exploited in the wild.
How severe is CVE-2024-21670?
Low severity, with a CVSS score of 3.1, published 16 January 2024.
Which products and versions are affected?
anoncreds-clsignatures (crates.io) SEMVER:introduced=0; ursa (crates.io) SEMVER:introduced=0,last_affected=0.3.7.
Is there a fix for CVE-2024-21670?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2024-21670?
Check whether you run anoncreds-clsignatures (crates.io) or ursa (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • anoncreds-clsignatures (crates.io) SEMVER:introduced=0
  • ursa (crates.io) SEMVER:introduced=0,last_affected=0.3.7

Identifiers

  • CVE-2024-21670
  • GHSA-r78f-4q2q-hvv4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.