Vulnerability · Published Aug 1, 2024 · Assigned by GitHub_M
CVE-2024-41948biscuit-java vulnerable to public key confusion in third party block
Low 3.0
In plain English
A low-severity security flaw in biscuit-java from biscuit-auth. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 21% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Maven | org.biscuitsec:biscuit | 4.0.0 | GHSA-5hcj-rwm6-xmw4 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| biscuit-auth | biscuit-java | >= 3.0.0, < 4.0.0 |
Weakness: CWE-1259 · Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N