Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/biscuit-auth/biscuit-go

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.8GoPublished

    Signature forgery in Biscuit

    CVE-2022-31053 · GHSA-75rw-34q6-72cr

    Affected
    • Go github.com/biscuit-auth/biscuit-go < 2.0.0
    Fixed in
    2.0.0· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 2.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →