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.
References
Configurations
No configuration.
History
06 Aug 2024, 16:30
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
05 Aug 2024, 20:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-08-05 20:15
Updated : 2024-08-06 16:30
NVD link : CVE-2024-42350
Mitre link : CVE-2024-42350
CVE.ORG link : CVE-2024-42350
JSON object : View
Products Affected
No product.
CWE
CWE-668
Exposure of Resource to Wrong Sphere