Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. ursa
  4. ›
  5. CVE-2024-21670

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

January 16, 2024 (updated January 19, 2024)

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.

References

  • github.com/advisories/GHSA-r78f-4q2q-hvv4
  • github.com/hyperledger-archives/ursa
  • github.com/hyperledger-archives/ursa/security/advisories/GHSA-r78f-4q2q-hvv4
  • nvd.nist.gov/vuln/detail/CVE-2024-21670

Code Behaviors & Features

Detect and mitigate CVE-2024-21670 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions up to 0.3.7

Solution

Unfortunately, there is no solution available yet.

Impact 8.1 HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Learn more about CVSS

Weakness

  • CWE-327: Use of a Broken or Risky Cryptographic Algorithm

Source file

cargo/ursa/CVE-2024-21670.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:15:59 +0000.