biscuit-auth biscuit 3 exposure of resource

Summaryinfo

A vulnerability was found in biscuit-auth biscuit. It has been declared as problematic. This vulnerability affects unknown code. Such manipulation leads to exposure of resource. This vulnerability is referenced as CVE-2024-42350. It is possible to launch the attack remotely. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in biscuit-auth biscuit and classified as problematic. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a exposure of resource vulnerability. Using CWE to declare the problem leads to CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. Impacted is integrity. CVE summarizes:

Biscuit is an authorization token with decentralized verification, offline attenuation and strong security policy enforcement based on a logic language. Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a `ThirdPartyBlock` request can be sent, providing only the necessary info to generate a third-party block and to sign it: 1. the public key of the previous block (used in the signature), 2. the public keys part of the token symbol table (for public key interning in datalog expressions). A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair. Tokens with third-party blocks containing `trusted` annotations generated through a third party block request. This has been addressed in version 4 of the specification. Users are advised to update their implementations to conform. There are no known workarounds for this vulnerability.

The advisory is available at github.com. This vulnerability is handled as CVE-2024-42350 since 07/30/2024. The exploitation is known to be difficult. The attack may be launched remotely. The exploitation requires an enhanced level of successful authentication. The technical details are unknown and an exploit is not available.

Upgrading to version 4 eliminates this vulnerability.

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

Productinfo

Vendor

• biscuit-auth

Name

• biscuit

Version

• 3

Website

• Product: https://github.com/biscuit-auth/biscuit/

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