CVE-2021-21291: Subdomain checking of whitelisted domains could allow unintended redirects
OAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. In OAuth2 Proxy before version 7.0.0, for users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect. For example, if a whitelist domain was configured for ".example.com", the intention is that subdomains of example.com are allowed. Instead, "example.com" and "badexample.com" could also match. This is fixed in version 7.0.0 onwards. As a workaround, one can disable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2021-21291?
CVE-2021-21291 has been classified as a high severity vulnerability due to potential unauthorized access to user accounts.
How do I fix CVE-2021-21291?
To fix CVE-2021-21291, upgrade to OAuth2 Proxy version 7.0.0 or later.
What does CVE-2021-21291 affect?
CVE-2021-21291 affects OAuth2 Proxy versions prior to 7.0.0 that implement the whitelist domain feature.
What are the risks associated with CVE-2021-21291?
The risks of CVE-2021-21291 include potential account takeover and unauthorized access for users relying on domain whitelisting.
Who is impacted by CVE-2021-21291?
Users of OAuth2 Proxy versions before 7.0.0 that utilize the whitelist domain feature are primarily impacted by CVE-2021-21291.