CVE-2020-11053: Open Redirect in OAuth2 Proxy

Published May 7, 2020
·
Updated

Impact As 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 (eg. %0a, %0b,%09,%0d) the validation could be bypassed and allow a redirect to any URL provided.

Patches @rootxharsh and @iamnoooob provided this patch as potential solution: From 4b941f56eda310b5c4dc8080b7635a6bfabccad4 Mon Sep 17 00:00:00 2001 From: Harsh Jaiswal <harsh@pop-os.localdomain> Date: Fri, 1 May 2020 20:38:31 +0530 Subject: [PATCH] Fixes redirect issue

--- oauthproxy.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/oauthproxy.go b/oauthproxy.go index 1e9bb7c..f8beb4d 100644 --- a/oauthproxy.go +++ b/oauthproxy.go @@ -577,8 +577,9 @@ func validOptionalPort(port string) bool {

// IsValidRedirect checks whether the redirect URL is whitelisted func (p OAuthProxy) IsValidRedirect(redirect string) bool { + matched, := regexp.MatchString(^/\s+/|\\, redirect) switch { - case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !strings.HasPrefix(redirect, "/\\"): + case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !matched: return true case strings.HasPrefix(redirect, "http://") || strings.HasPrefix(redirect, "https://"): redirectURL, err := url.Parse(redirect) -- 2.17.1

This issue was also reported to us separately by @mik317 several hours later

The fix was implemented in #xxx and released as version 5.1.1

Other sources

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.

Affected Software

2 affected componentsFixes available
go/github.com/oauth2-proxy/oauth2-proxy<5.1.1
5.1.1
Oauth2 Proxy Project Oauth2 Proxy<5.1.1

Event History

May 7, 2020
CVE Published
via MITRE·08:30 PM
Data Sourced
via MITRE·08:30 PM
DescriptionSeverityWeakness
Dec 20, 2021
Advisory Published
via GitHub·05:59 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-11053?

CVE-2020-11053 is classified as a high-severity vulnerability due to the potential for open redirect attacks.

2

How do I fix CVE-2020-11053?

To address CVE-2020-11053, update the oauth2-proxy to version 5.1.1 or later.

3

What types of software are affected by CVE-2020-11053?

CVE-2020-11053 affects oauth2-proxy prior to version 5.1.1.

4

What kind of attack can exploit CVE-2020-11053?

CVE-2020-11053 can be exploited through open redirect vulnerabilities leading to phishing or unintended redirection.

5

Is user authentication impacted by CVE-2020-11053?

Yes, CVE-2020-11053 can impact user authentication flows due to improper redirect URL validation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203