Authentication Bypass in github.com/ory/fosite (CVE-2020-15222)
Summary
Authentication bypass in github.com/ory/fosite (CVE-2020-15222). Confidential information can be exposed externally. Exploitable via jti. Mitigation: upgrade to 0.31.0 or later.
Original description
The description as published by the source.
In ORY Fosite (the security first OAuth2 & OpenID Connect framework for Go) before version 0.31.0, when using "private_key_jwt" authentication the uniqueness of the jti value is not checked. When using client authentication method "private_key_jwt", OpenId specification says the following about assertion jti: "A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties". Hydra does not seem to check the uniqueness of this jti value. This problem is fixed in version 0.31.0.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-15222 has been found in github.com/ory/fosite.
Attackers can target a specific entry point like jti over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade github.com/ory/fosite to 0.31.0 or later.
If unsure, ask your IT team or search "github.com/ory/fosite CVE-2020-15222" on the vendor's site.
CVE-2020-15222 (github.com/ory/fosite) — CWE-287
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: jti
Patched: 0.31.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in github.com/ory/fosite. Attackers reach the vulnerable code path via jti without authentication.
Check the vendor advisory for the affected versions of github.com/ory/fosite. Attack surface: jti.
Severity: ?. Confidential information can be exposed externally.
Update to 0.31.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/ory/fosite' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/ory/fosite' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/ory/fositeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/ory/fosite to 0.31.0ステージング環境で 0.31.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory openid.net
- package github.com
- patch github.com
- report github.com
- web github.com
- web pkg.go.dev