CVE-2020-5233: Open Redirect in OAuth2 Proxy
Published Jan 30, 2020
·Updated
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.
Affected Software
1 affected component
Oauth2 Proxy Project Oauth2 Proxy<5.0.0
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OAuth2 Proxyto a version that resolves this vulnerability.Fixed in 5.0
Event History
Jan 30, 2020
CVE Published
via MITRE·05:45 PM
Data Sourced
via MITRE·05:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2020-5233?
CVE-2020-5233 is considered a medium severity vulnerability due to the potential for authentication token harvesting.
2
How do I fix CVE-2020-5233?
To fix CVE-2020-5233, upgrade to OAuth2 Proxy version 5.0 or later.
3
What kind of vulnerability is CVE-2020-5233?
CVE-2020-5233 is an open redirect vulnerability affecting OAuth2 Proxy.
4
Who is affected by CVE-2020-5233?
Any users running OAuth2 Proxy versions prior to 5.0 are affected by CVE-2020-5233.
5
What can happen if CVE-2020-5233 is exploited?
If exploited, CVE-2020-5233 could allow attackers to silently harvest authentication tokens.