Signature forgery in Biscuit
biscuit-auth biscuit
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| biscuit-auth crates.io |
|
|
| github.com/biscuit-auth/biscuit-go Go |
|
|
biscuit-auth biscuit
| Product | Affected | Fixed in |
|---|---|---|
| biscuit-auth crates.io |
|
|
| github.com/biscuit-auth/biscuit-go Go |
|
|
|
|
Biscuit is an authentication and authorization token for microservices architectures. The Biscuit specification version 1 contains a vulnerable algorithm that allows malicious actors to forge valid Γ-signatures. Such an attack would allow an attacker to create a token with any access level. 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 are no known workarounds for this issue.
From the CVE record · GitHub_M
Biscuit specification version 1 uses a vulnerable Γ-signature algorithm. An attacker can forge a valid signature and create a token with any access level. The input does not specify whether network access, prior authentication, or user interaction is required.
Teams using biscuit-auth >=1.0.0 and <2.0.0, biscuit-go versions before 2.0.0, or biscuit-java versions before 2.0.0 should check their deployments.