CVE-2022-31053
CRITICALCVE-2022-31053 is a critical-severity (CVSS 9.8) CWE-347 vulnerability in biscuit-auth. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2022-31053 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Signature forgery in Biscuit
Blast Radius
biscuit-auth🐹github.com/biscuit-auth/biscuit-go☕com.clever-cloud:biscuit-javaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io, Go, Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | biscuit-auth | ≥ 1.0.0&&< 2.0.0 | 2.0.0 |
| 🐹Go | github.com/biscuit-auth/biscuit-go | all versions | 2.0.0 |
| ☕Maven | com.clever-cloud:biscuit-java | all versions | 2.0.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for biscuit-auth. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update biscuit-auth to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31053 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-31053 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-31053. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-31053 in your dependencies?
O3 detects CVE-2022-31053 across crates.io, Go, Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.