CVE-2024-41948
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.
Scoring
- Severity
- LOW
- CVSS base score
- 3
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N
- EPSS probability
- 0.28%
- CWE
- CWE-1259
- Published
- 2024-08-01
- Last modified
- 2026-03-13
Affected products
- biscuit-auth biscuit-java
Weakness type
Related vulnerabilities
- CVE-2026-58429 — Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints
- CVE-2026-54593 — Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions
- CVE-2026-25700 — Apache Answer: AdminToken not invalidated after admin deactivation
- CVE-2026-40264 — OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation
- CVE-2024-45448 — Page table protection configuration vulnerability in the trusted firmware module...
- CVE-2024-36111 — KubePi's JWT token validation has a defect
- CVE-2022-23541 — jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC
- CVE-2022-23551 — AAD Pod Identity obtaining token with backslash