biscuit-auth
Affected
- introduced
1.0.0, fixed2.0.0(semver)
Fixed versions
2.0.0
Fix
- Fixed version
2.0.0cargo update -p biscuit-auth --precise 2.0.0
Advisory
Also known as: CVE-2022-31053, GO-2022-0564, HSEC-2023-0002
Signature forgery in Biscuit
Impact
The paper Cryptanalysis of Aggregate Γ-Signature and Practical Countermeasures in Application to Bitcoin defines a way to forge valid Γ-signatures, an algorithm that is used in the Biscuit specification version 1.
It would allow an attacker to create a token with any access level.
As Biscuit v1 was still an early version and not broadly deployed, we were able to contact all known users of Biscuit v1 and help them migrate to Biscuit v2.
We are not aware of any active exploitation of this vulnerability.
Patches
The version 2 of the specification mandates a different algorithm than gamma signatures and as such is not affected by this vulnerability. The Biscuit implementations in Rust, Haskell, Go, Java and Javascript all have published versions following the v2 specification.
Workarounds
There is no known workaround, any use of Biscuit v1 should be migrated to v2.
References
Cryptanalysis of Aggregate Γ-Signature and Practical Countermeasures in Application to Bitcoin
For more information
If you have any questions or comments about this advisory:
Critical Basis: The source's own band: CRITICAL
1.0.0, fixed 2.0.0 (semver)2.0.0
2.0.0cargo update -p biscuit-auth --precise 2.0.00, fixed 2.0.0 (semver)2.0.0
2.0.0go get github.com/biscuit-auth/[email protected]Fix 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