Security readout for executives and security teams
Plain-English summary
Biscuit version 1 tokens can be forged because the specification used a vulnerable signature algorithm. If an application trusts these tokens for authorization, an attacker could create a token with any access level. Version 2 changes the algorithm and is stated as not affected.
Executive priority
Treat this as urgent where Biscuit is used for access control. The business risk is unauthorized privilege creation, not just service disruption. If Biscuit is not deployed, no direct action is indicated beyond dependency confirmation.
Technical view
CVE-2022-31053 is a CWE-347 signature forgery issue in Biscuit specification v1 Γ-signatures. The advisory lists affected Rust, Haskell, Java, and Go implementations before v2 or at a specific Haskell version. CVSS 3.1 is 9.8, reflecting network reachability, no privileges, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to services using Biscuit authorization tokens with the v1 specification or the listed affected package versions. Organizations not using Biscuit are not exposed based on the provided sources.
Exploitation context
The provided bundle does not show CISA KEV listing or known active exploitation. The risk remains severe because successful forgery could create arbitrary access-level tokens without needing prior privileges or user interaction.
Researcher notes
Evidence names the vulnerable design as Biscuit spec v1 Γ-signatures and states v2 mandates a different algorithm. The source bundle does not provide exploit details, active exploitation evidence, or a workaround beyond moving to v2 implementations.
Mitigation direction
- Upgrade Biscuit implementations to versions following the v2 specification where available.
- Prioritize replacement of any Biscuit v1 token issuer or verifier.
- If immediate upgrade is blocked, check current vendor guidance before choosing compensating controls.
- Do not treat v1 Biscuit tokens as a sufficient authorization boundary.
- Track all services that issue, validate, or forward Biscuit tokens.
Validation and detection
- Inventory dependencies for biscuit-auth, biscuit-haskell, biscuit-java, and biscuit-go.
- Confirm no service uses Biscuit specification version 1.
- Verify token issuers and token validators are both on v2-compatible implementations.
- Review authorization services for any remaining Γ-signature validation path.
- Check access logs for unexpected privileged activity around Biscuit-protected services.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-31053 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/biscuit-auth/biscuit/security/advisories/GHSA-75rw-34q6-72crCVE reference · x_refsource_CONFIRM
- https://eprint.iacr.org/2020/1484CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.