Open Redirect in github.com/oauth2-proxy/oauth2-proxy (CVE-2020-4037)
Summary
Vulnerability in github.com/oauth2-proxy/oauth2-proxy (CVE-2020-4037). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.0.0 or later.
Original description
The description as published by the source.
In OAuth2 Proxy from version 5.1.1 and less than version 6.0.0, users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access. This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites. This has been fixed in version 6.0.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-4037 has been found in github.com/oauth2-proxy/oauth2-proxy.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/oauth2-proxy/oauth2-proxy to 6.0.0 or later.
If unsure, ask your IT team or search "github.com/oauth2-proxy/oauth2-proxy CVE-2020-4037" on the vendor's site.
CVE-2020-4037 (github.com/oauth2-proxy/oauth2-proxy) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated
Patched: 6.0.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.
A vulnerability (CWE-601) exists in github.com/oauth2-proxy/oauth2-proxy.
Check the vendor advisory for the affected versions of github.com/oauth2-proxy/oauth2-proxy.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.0.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/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 patch patch
Upgrade github.com/oauth2-proxy/oauth2-proxy to 6.0.0ステージング環境で 6.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com