Vulnerability in Biscuit-Auth Biscuit
CVE-2024-42350
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.
EPSS: 0.003 (21.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 3.0 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N.
Affected products
- Biscuit-auth Biscuit — versions < 4
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM)
- security-advisories@github.com (x_refsource_MISC)
Frequently asked questions
- What is CVE-2024-42350?
- CVE-2024-42350 is a low-severity vulnerability in Biscuit-Auth Biscuit, classified under Exposure of Resource to Wrong Sphere. CVSS score: 3.0/10. Published 2024-08-05.
- How severe is CVE-2024-42350?
- Low severity. CVSS v3 base score is 3.0 out of 10.