GitHub Advisoryadvisory · crates.io, Go, Maven

GHSA-75rw-34q6-72cr Signature forgery in Biscuit

CRITICAL Published 2022-06-17 Modified 2023-03-07 Official page ↗
Aliases
CVE-2022-31053
Ecosystem
crates.io, Go, Maven
Packages
biscuit-auth, github.com/biscuit-auth/biscuit-go, com.clever-cloud:biscuit-java
Severity
Critical
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-347
Reviewed
2022-06-17

Affected packages

• crates.io biscuit-auth: >= 1.0.0, < 2.0.0 → fixed in 2.0.0 • Go github.com/biscuit-auth/biscuit-go: < 2.0.0 → fixed in 2.0.0 • Maven com.clever-cloud:biscuit-java: < 2.0.0 → fixed in 2.0.0

Description

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: • Open an issue in biscuit-auth/biscuit • Ask questions on Matrix

Related

Alias · CVE (1)

  • CVE-2022-31053 Biscuit is an authentication and authorization token for microservices architectures. vulnerability

Weakness · CWE (1)

  • CWE-347 Improper Verification of Cryptographic Signature weakness

References