Vulnerability 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.
CVSS Score
LOW
Related Weaknesses (CWE)
References
- https://github.com/biscuit-auth/biscuit/commit/c87cbb5d778964d6574df3e9e6579567c
- https://github.com/biscuit-auth/biscuit/security/advisories/GHSA-rgqv-mwc3-c78m
FAQ
What is CVE-2024-42350?
CVE-2024-42350 is a vulnerability with a CVSS score of 3.0 (LOW). 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 tra...
How severe is CVE-2024-42350?
CVE-2024-42350 has been rated LOW with a CVSS base score of 3.0/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-42350?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.