Biscuit Java
Approved changes feed: RSS · Atom
cpe:2.3:a:biscuitsec:biscuit-java:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Biscuitsec (28380834-74f6-59cc-af69-3f4e43ed8fd7) |
|---|---|
| Product | Biscuit Java (26838dd5-4b9c-57bc-ba8b-dd0ab230c0b1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/biscuit-auth/biscuit-java |
purl2cpe | 2026-06-01 10:14:43.289684 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-41948 |
vulnerable | 2026-06-08 06:43:55.728730 |
biscuit-java vulnerable to public key confusion in third party block
LOW (3)
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.
Published: 2024-08-01T22:03:15.788Z
Updated: 2024-08-07T14:59:20.577Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.