Hyperledger ursa up to 0.3.7 inclusion of functionality from untrusted control sphere

Summaryinfo

A vulnerability, which was classified as problematic, was found in Hyperledger ursa up to 0.3.7. This affects an unknown part. Such manipulation leads to inclusion of functionality from untrusted control sphere. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is referenced as CVE-2022-31021. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability was found in Hyperledger ursa up to 0.3.7 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. Using CWE to declare the problem leads to CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. Impacted is confidentiality. CVE summarizes:

Ursa is a cryptographic library for use with blockchains. A weakness in the Hyperledger AnonCreds specification that is not mitigated in the Ursa and AnonCreds implementations is that the Issuer does not publish a key correctness proof demonstrating that a generated private key is sufficient to meet the unlinkability guarantees of AnonCreds. The Ursa and AnonCreds CL-Signatures implementations always generate a sufficient private key. A malicious issuer could in theory create a custom CL Signature implementation (derived from the Ursa or AnonCreds CL-Signatures implementations) that uses weakened private keys such that presentations from holders could be shared by verifiers to the issuer who could determine the holder to which the credential was issued. This vulnerability could impact holders of AnonCreds credentials implemented using the CL-signature scheme in the Ursa and AnonCreds implementations of CL Signatures. The ursa project has has moved to end-of-life status and no fix is expected.

The weakness was published 01/17/2024 as GHSA-2q6j-gqc4-4gw3. The advisory is available at github.com. This vulnerability is handled as CVE-2022-31021 since 05/18/2022. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 02/10/2024).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• Hyperledger

Name

• ursa

Version

• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6
• 0.3.7

Support

• end of life

Website

• Product: https://github.com/hyperledger/ursa/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion