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

> A flaw in Ursa's revocation scheme allows malicious verifiers to generate unique identifiers for holders, compromising privacy in verifiable presentations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Jan 2024
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-6698-mhxx-r84g

## What is CVE-2024-22192?

CVE-2024-22192 is a medium-severity vulnerability in hyperledger-archives ursa, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Ursa is a cryptographic library for use with blockchains. 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. 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. Ursa has moved to end-of-life status and no fix is expected.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2024-22192?

4 open source packages ship an affected version, including ursa and anoncreds-clsignatures. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ursa` | crates.io | All versions to 0.3.7 | None |
| `ursa` | crates.io | All versions to 0.3.7 | None |
| `anoncreds-clsignatures` | crates.io | All versions | 0.1.0 |
| `anoncreds-clsignatures` | crates.io | All versions | 0.1.0 |

Products: Hyperledger Ursa.

## How do I fix CVE-2024-22192?

Product is end of life, replace it.

## Is CVE-2024-22192 being exploited?

There is no known exploitation of CVE-2024-22192 in the wild and no public exploit code.

## Other vulnerabilities in hyperledger-archives ursa

- [CVE-2024-21670](https://insights.sbomify.com/CVE-2024-21670/): CL-Signatures Revocation Scheme in Ursa has flaws that allow a holder to demonstrate non-revocation of a revoked credential (medium 6.5)
- [CVE-2022-31021](https://insights.sbomify.com/CVE-2022-31021/): Unlinkability broken in ursa when verifiers use malicious keys (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22192 and fix it if it is affected.

What it is: CVE-2024-22192 is a medium-severity vulnerability in hyperledger-archives ursa, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22192 in the wild and no public exploit code.

Affected packages and fixed versions:
- ursa (crates.io): affected all versions up to 0.3.7; no fix listed
- ursa (crates.io): affected all versions up to 0.3.7; no fix listed
- anoncreds-clsignatures (crates.io): affected all versions; fixed in 0.1.0
- anoncreds-clsignatures (crates.io): affected all versions; fixed in 0.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22192/ (Markdown: https://insights.sbomify.com/CVE-2024-22192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22192
- OSV: https://osv.dev/vulnerability/CVE-2024-22192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22192/
Summaries are generated and may contain mistakes; the official description above is the record.