Loading...
Skip to main content

CVE-2022-31053 — Signature forgery in...

CRITICAL

Signature forgery in Biscuit

Published June 17, 2022Updated February 4, 2026Source: osv

Summary

### Impact The paper [Cryptanalysis of Aggregate Γ-Signature and Practical Countermeasures in Application to Bitcoin](https://eprint.iacr.org/2020/1484) 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](https://eprint.iacr.org/2020/1484) ### For more information If you have any questions or comments about this advisory: * Open an issue in [biscuit-auth/biscuit](https://github.com/biscuit-auth/biscuit) * Ask questions on [Matrix](https://matrix.to/#/#biscuit-auth:matrix.org)

Advisory Timeline

  • First published June 17, 2022 (1578 days ago).
  • Last revised February 4, 2026 — 1328 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update com.clever-cloud:biscuit-java to 2.0.0 or later
<!-- Update pom.xml dependency version to 2.0.0 for com.clever-cloud:biscuit-java -->
Cargo
Update biscuit-auth to 2.0.0 or later
cargo update -p biscuit-auth --precise 2.0.0
Go
Update github.com/biscuit-auth/biscuit-go to 2.0.0 or later
go get github.com/biscuit-auth/biscuit-go@v2.0.0

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (3)

Affects 3 ecosystems: crates.io (1), go (1), maven (1).

PackageEcosystemAffectedFixed In
com.clever-cloud:biscuit-java
maven
0.2.1, 0.2.2, 0.2.3, 0.2.4 (+18 more)2.0.0
biscuit-auth
crates.io
All versions2.0.0
github.com/biscuit-auth/biscuit-go
go
All versions2.0.0

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-347
    Improper Verification of Cryptographic SignatureMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.8 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2022-31053?
Signature forgery in Biscuit This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.8/10).
How do I check if my project is affected by CVE-2022-31053?
CVE-2022-31053 affects com.clever-cloud:biscuit-java, biscuit-auth and github.com/biscuit-auth/biscuit-go. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2022-31053 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.8

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-75rw-34q6-72cr
GO-2022-0564
HSEC-2023-0002

Related CVEs

  • CVE-2026-107806
    CRITICAL

    Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite

  • CVE-2026-68582
    CRITICAL

    Vikunja: Link-share token reads any tenant's kanban buckets and enumerates usernames/IDs instance-wide (BOLA)

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies