biscuit-auth biscuit-java 3.x improper restriction of security token assignment

Summaryinfo

A vulnerability classified as problematic has been found in biscuit-auth biscuit-java 3.x. This vulnerability affects unknown code. The manipulation leads to improper restriction of security token assignment. This vulnerability is traded as CVE-2024-41948. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in biscuit-auth biscuit-java 3.x. It has been rated as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a improper restriction of security token assignment vulnerability. Using CWE to declare the problem leads to CWE-1259. The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected. Impacted is integrity. The summary by CVE is:

biscuit-java is the java implementation of Biscuit, an authentication and authorization token for microservices architectures. 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, which includes the public key of the previous block (used in the signature) and 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. This vulnerability is fixed in 4.0.0.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-41948 since 07/24/2024. The exploitation is known to be difficult. The attack may be initiated remotely. Additional levels of successful authentication are needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1134.001 according to MITRE ATT&CK.

Upgrading to version 4.0.0 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Programming Language Software

Vendor

• biscuit-auth

Name

• biscuit-java

Version

• 3.x

Website

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

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion