Open Redirect in github.com/oauth2-proxy/oauth2-proxy (CVE-2020-5233)
Summary
Vulnerability in github.com/oauth2-proxy/oauth2-proxy (CVE-2020-5233). Data can be tampered with by attackers. Exploitable via oauth2_proxy. Mitigation: upgrade to 5.0.0 or later.
Original description
The description as published by the source.
OAuth2 Proxy before 5.0 has an open redirect vulnerability. Authentication tokens could be silently harvested by an attacker. This has been patched in version 5.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-5233 has been found in github.com/oauth2-proxy/oauth2-proxy.
Attackers can target a specific entry point like oauth2_proxy over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade github.com/oauth2-proxy/oauth2-proxy to 5.0.0 or later.
If unsure, ask your IT team or search "github.com/oauth2-proxy/oauth2-proxy CVE-2020-5233" on the vendor's site.
CVE-2020-5233 (github.com/oauth2-proxy/oauth2-proxy) — CWE-601
Attack vector: remote (network-reachable)
Attack surface: oauth2_proxy
Patched: 5.0.0 — apply immediately
Workaround: At this stage there is no work around.
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.
A vulnerability (CWE-601) exists in github.com/oauth2-proxy/oauth2-proxy. Attackers reach the vulnerable code path via oauth2_proxy.
Check the vendor advisory for the affected versions of github.com/oauth2-proxy/oauth2-proxy. Attack surface: oauth2_proxy.
Severity: ?. Data can be tampered with by attackers.
Update to 5.0.0.
Workaround: At this stage there is no work around.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/oauth2-proxy/oauth2-proxy' . 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/oauth2-proxy/oauth2-proxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/oauth2-proxy/oauth2-proxyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
At this stage there is no work around.パッチが適用されるまでの応急処置として、At this stage there is no work around. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/oauth2-proxy/oauth2-proxy to 5.0.0ステージング環境で 5.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory github.com
- web github.com
- web nvd.nist.gov
- web github.com
- web blog.detectify.com
- web github.com