biscuit-auth
Affected
- introduced
4.0.0, fixed5.0.0(semver)
Fixed versions
5.0.0
Fix
- Fixed version
5.0.0cargo update -p biscuit-auth --precise 5.0.0
Advisory
Also known as: CVE-2024-41949, CVE-2024-42350, GHSA-47cq-pc2v-3rmp, GHSA-rgqv-mwc3-c78m, HSEC-2024-0009
biscuit-auth vulnerable to public key confusion in third party block
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:
A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair.
Consider the following example (nominal case)
A emits the following token: check if thirdparty("b") trusting ${pubkeyB}BB generates the following third-party block thirdparty("b"); check if thirdparty("c") trusting ${pubkeyC}C to be able to use the tokenNow, with a malicious user:
A emits the following token: check if thirdparty("b") trusting ${pubkeyB}thirdparty("c"), signed with a keypair pubkeyD, privkeyD) they generateThirdPartyBlockRequest publicKeys field and replace pubkeyD with pubkeyCB generates the following third-party block thirdparty("b"); check if thirdparty("c") trusting ${pubkeyC}thirdparty("b"); check if thirdparty("c") trusting ${pubkeyD}C.Impact
Tokens with third-party blocks containing trusted annotations generated through a third party block request
Low Basis: The source's own band: LOW
4.0.0, fixed 5.0.0 (semver)5.0.0
5.0.0cargo update -p biscuit-auth --precise 5.0.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0