Vulnerability Description
In OAuth2 Proxy before 5.1.1, there is an open redirect vulnerability. 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. However, by crafting a redirect URL with HTML encoded whitespace characters the validation could be bypassed and allow a redirect to any URL provided. This has been patched in 5.1.1.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Oauth2 Proxy Project | Oauth2 Proxy | < 5.1.1 |
Related Weaknesses (CWE)
References
- https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-j7px-6hwj-Vendor Advisory
- https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-j7px-6hwj-Vendor Advisory
FAQ
What is CVE-2020-11053?
CVE-2020-11053 is a vulnerability with a CVSS score of 7.1 (HIGH). In OAuth2 Proxy before 5.1.1, there is an open redirect vulnerability. Users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This ...
How severe is CVE-2020-11053?
CVE-2020-11053 has been rated HIGH with a CVSS base score of 7.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-11053?
Check the references section above for vendor advisories and patch information. Affected products include: Oauth2 Proxy Project Oauth2 Proxy.