CVE-2024-22192: Ursa CL-Signatures Revocation allows verifiers to generate unique identifiers for holders

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

Ursa CL-Signatures Revocation allows verifiers to generate unique identifiers for holders

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

Quick answers

Is CVE-2024-22192 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-22192 being exploited in the wild.
How severe is CVE-2024-22192?
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,fixed=0.1.0; ursa (crates.io) SEMVER:introduced=0,last_affected=0.3.7.
Is there a fix for CVE-2024-22192?
Yes. anoncreds-clsignatures (crates.io): upgrade to 0.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-22192?
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.

How to fix

  • anoncreds-clsignatures (crates.io): upgrade to 0.1.0 or later
    cargo update -p anoncreds-clsignatures

Affected products

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

Identifiers

  • CVE-2024-22192
  • GHSA-6698-mhxx-r84g

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