CPE Details
oauth2 proxy Project oauth2 proxy 2.1
2.1
2020-03-03
16h41 +00:00
16h41 +00:00
2020-03-03
16h41 +00:00
16h41 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:a:oauth2_proxy_project:oauth2_proxy:2.1:*:*:*:*:*:*:*
Informations
Vendor
oauth2_proxy_projectProduct
oauth2_proxyVersion
2.1Related CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
| 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. | 6.1 |
Medium |
||
| 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. | 7.1 |
High |
||
| 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. | 6.1 |
Medium |
||
| CSRF in Bitly oauth2_proxy 2.1 during authentication flow | 8.8 |
High |
||
| The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and termination of the 2-legged OAuth flow. This issue was caused by improper input validation and a violation of RFC-6819 | 6.1 |
Medium |
2025©
tesweb SA
