CVE-2024-22192: Ursa Ursa CL-Signatures Revocation Allows Verifiers Vulnerability

MODERATE
Advisory Identifier: GHSA-6698-mhxx-r84g
CVSS 6.5
CWE-327
Published
Advisory Summary

CVE-2024-22192 is a MODERATE (CVSS 6.5) ursa cl-signatures revocation allows verifiers vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Ursa libraries in the crates.io ecosystem. The issue involves ursa cl-signatures revocation allows verifiers to generate unique identifiers for holders. Remediation is available by upgrading affected packages to version 0.1.0.

CVE-2024-22192 at a Glance

CVE Identifier CVE-2024-22192
GHSA Identifier GHSA-6698-mhxx-r84g
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Ursa
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2024-22192

To remediate this vulnerability, upgrade all affected Ursa dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

ursa fixed: Latest secure release
Upgrade ursa to Latest secure release
anoncreds-clsignatures fixed: 0.1.0
Upgrade anoncreds-clsignatures to 0.1.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for ursa

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-22192, inspect your project dependencies for Ursa:

inspect dependencies for ursa

Analyze the terminal output to locate any version of Ursa in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Ursa, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The revocation scheme 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. Notably, a malicious verifier may be able to generate a unique identifier for a holder providing a verifiable presentation that includes a Non-Revocation proof. ### Details The revocation scheme 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, potentially allowing a malicious verifier to generate a unique identifier for a holder that provides a verifiable presentation that includes a Non-Revocation proof. The flaws affects all CL-Signature versions published from the [Hyperledger Ursa] repository to the [Ursa Rust Crate], and is fixed in all versions published from the [Hyperledger AnonCreds CL-Signatures] repository to the [AnonCreds CL-Signatures Rust Crate]. The addressing the flaw requires updating AnonCreds holder software (such as mobile wallets) to a corrected CL-Signature implementation, such as the [AnonCreds CL Signatures Rust Crate]. Verifying presentations from corrected holders requires a updating the verifier software to a corrected CL-Signatures implementation. An updated verifier based on AnonCreds CL-Signatures can verify presentations from holders built on either the flawed Ursa CL-Signature implementation or a corrected CL-Signature implementation [Hyperledger Ursa]: https://github.com/hyperledger-archives/ursa [Ursa Rust Crate]: https://crates.io/crates/ursa [Hyperledger AnonCreds CL-Signatures]: https://github.com/hyperledger/anoncreds-clsignatures-rs [AnonCreds CL-Signatures Rust Crate]: https://crates.io/crates/anoncreds-clsignatures The flaw occurs as a result of generating a verifiable presentation that includes a Non-Revocation proof from a flawed implementation. ### Impact The impact of the flaw is that a malicious verifier may be able to determine a unique identifier for a holder presenting a Non-Revocation proof. ### Mitigation Upgrade libraries/holder applications that generate AnonCreds verifiable presentations using the [Ursa Rust Crate] to any version of the [AnonCreds CL-Signatures Rust Crate].

CVE-2024-22192 Affected Ursa Versions

2 component(s)
Fixed Versions:
0.1.0
Product / Package Ecosystem Affected Versions Fixed Version
ursa
crates.io
≤ 0.3.7
anoncreds-clsignatures
crates.io
< 0.1.0
0.1.0

References

Frequently Asked Questions

What is CVE-2024-22192?
CVE-2024-22192 is a security vulnerability in Ursa involving Ursa CL-Signatures Revocation allows verifiers to generate unique identifiers for holders under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Ursa versions are affected?
Affected versions include releases prior to 0.1.0 across affected packages: ursa, anoncreds-clsignatures.
What version fixes CVE-2024-22192?
Upgrading to 0.1.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ursa affected?
Yes, ursa is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
Is anoncreds-clsignatures affected?
Yes, anoncreds-clsignatures is affected in releases prior to 0.1.0. Upgrade your dependency to 0.1.0 or later.
What is the CVSS score of CVE-2024-22192?
CVE-2024-22192 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2024-22192?
CVE-2024-22192 is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check crates.io dependencies for CVE-2024-22192?
Run the dependency tree command: 'inspect dependencies for ursa'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6698-mhxx-r84g",
  "modified" : "2024-01-19T19:28:25Z",
  "published" : "2024-01-16T21:13:40Z",
  "aliases" : [ "CVE-2024-22192" ],
  "summary" : "Ursa CL-Signatures Revocation allows verifiers to generate unique identifiers for holders",
  "details" : "### Summary\n\nThe revocation scheme 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. Notably, a malicious verifier may be able to generate a unique identifier for a holder providing a verifiable presentation that includes a Non-Revocation proof.\n\n### Details\n\nThe revocation scheme 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, potentially allowing a malicious verifier to generate a unique identifier for a holder that provides a verifiable presentation that includes a Non-Revocation proof.\n\nThe flaws affects all CL-Signature versions published from the [Hyperledger Ursa] repository to the [Ursa Rust Crate], and is fixed in all versions published from the [Hyperledger AnonCreds CL-Signatures] repository to the [AnonCreds CL-Signatures Rust Crate].\n\nThe addressing the flaw requires updating AnonCreds holder software (such as mobile wallets) to a corrected CL-Signature implementation, such as the [AnonCreds CL Signatures Rust Crate]. Verifying presentations from corrected holders requires a updating the verifier software to a corrected CL-Signatures implementation. An updated verifier based on AnonCreds CL-Signatures can verify presentations from holders built on either the flawed Ursa CL-Signature implementation or a corrected CL-Signature implementation\n\n[Hyperledger Ursa]: https://github.com/hyperledger-archives/ursa\n[Ursa Rust Crate]: https://crates.io/crates/ursa\n[Hyperledger AnonCreds CL-Signatures]: https://github.com/hyperledger/anoncreds-clsignatures-rs\n[AnonCreds CL-Signatures Rust Crate]: https://crates.io/crates/anoncreds-clsignatures\n\nThe flaw occurs as a result of generating a verifiable presentation that includes a Non-Revocation proof from a flawed implementation.\n\n### Impact\nThe impact of the flaw is that a malicious verifier may be able to determine a unique identifier for a holder presenting a Non-Revocation proof.\n\n### Mitigation\n\nUpgrade libraries/holder applications that generate AnonCreds verifiable presentations using the [Ursa Rust Crate] to any version of the [AnonCreds CL-Signatures Rust Crate].",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "ursa"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.3.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "anoncreds-clsignatures"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.1.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/hyperledger-archives/ursa/security/advisories/GHSA-6698-mhxx-r84g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-22192"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/hyperledger/anoncreds-clsignatures-rs/commit/1e55780c890b027fa51e361e188a7743a0bf473f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/hyperledger-archives/ursa"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-01-16T21:13:40Z",
    "nvd_published_at" : "2024-01-16T22:15:46Z"
  }
}