Signature forgery in Biscuit
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.0.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- biscuit-auth biscuit
biscuit-haskell = 0.1.1.0, com.clever-cloud.biscuit-java < 2.0.0, github.com/biscuit-auth/biscuit-go < 2.0
- github.com/biscuit-auth/biscuit-goGo
All versions
- biscuit-authcrates.io
From 1.0.0 · fixed in 2.0.0
- github.com/biscuit-auth/biscuit-goGo
fixed in 2.0.0
- com.clever-cloud:biscuit-javaMaven
fixed in 2.0.0