Holder tracking via reusable non-revocation proof value
Published Jan 16, 2024 · Updated Jun 16, 2025
Privacy weakness in Hyperledger Ursa 0.3.7 and earlier allows remote attackers to identify credential holders via non-revocation proofs. The CL-Signatures prover encodes a separate m2 value derived from the credential context in each proof, so repeated presentations expose a stable link. A holder must present a credential with a non-revocation proof to a malicious verifier; integrity and availability are unaffected.
Summary
What happened
Privacy weakness in Hyperledger Ursa 0.3.7 and earlier allows remote attackers to identify credential holders via non-revocation proofs. The CL-Signatures prover encodes a separate m2 value derived from the credential context in each proof, so repeated presentations expose a stable link. A holder must present a credential with a non-revocation proof to a malicious verifier; integrity and availability are unaffected.
The record
- CVE
- CVE-2024-22192
- Published
- Jan 16, 2024
- Updated
- Jun 16, 2025
- Vendor
- Hyperledger Foundation
- Product
- Hyperledger Ursa
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2024CVE publishedPublication date reported by the CVE source.
- Jun 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 0.3.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo