CVE-2024-42350

Source
https://nvd.nist.gov/vuln/detail/CVE-2024-42350
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-42350.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2024-42350
Aliases
Published
2024-08-05T20:15:36Z
Modified
2024-10-08T04:27:03.437337Z
Summary
[none]
Details

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

Affected packages

Git / github.com/biscuit-auth/biscuit

Affected ranges

Type
GIT
Repo
https://github.com/biscuit-auth/biscuit
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed