CVE-2024-42350

Public key confusion in third party block in Biscuit

State
Published
Severity
3.0 Low
Published
Aug 5, 2024
Updated
Aug 5, 2024
Reserved
Jul 30, 2024

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.13.0 LowCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:NGitHub_M

Weaknesses

  • CWE-668 Exposure of Resource to Wrong Sphere

Affected Products

ProductVersions
biscuitbiscuit-auth
  • < 4Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.