| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/biscuit-auth/biscuit-go | < 2.0.0all versions | 2.0.0 |
| com.clever-cloud:biscuit-java | < 2.0.0 | 2.0.0 |
| biscuit-auth | ≥ 1.0.0, ≤ 1.1.0 | |
| biscuit-go | < 2.0.0 | 2.0.0 |
| biscuit-haskell | = 0.1.1.0 | |
| biscuit-java | < 2.0.0 | 2.0.0 |
| biscuit-auth | ≥ 1.0.0, < 2.0.0 | 2.0.0 |
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.
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.
There is no known workaround, any use of Biscuit v1 should be migrated to v2.
Cryptanalysis of Aggregate Γ-Signature and Practical Countermeasures in Application to Bitcoin
If you have any questions or comments about this advisory:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free