OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode
oauth2-proxy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/oauth2-proxy/oauth2-proxy/v7 Go |
|
|
| github.com/oauth2-proxy/oauth2-proxy Go |
| No fix yet |
oauth2-proxy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/oauth2-proxy/oauth2-proxy/v7 Go |
|
|
| github.com/oauth2-proxy/oauth2-proxy Go |
| No fix yet |
OAuth2 Proxy is a reverse proxy that provides authentication using OAuth2 providers. Versions prior to 7.15.2 contain a configuration-dependent authentication bypass in deployments where OAuth2 Proxy is used with an auth_request-style integration (such as nginx auth_request) and either --ping-user-agent is set or --gcp-healthchecks is enabled. In affected configurations, OAuth2 Proxy treats any request with the configured health check User-Agent value as a successful health check regardless of the requested path, allowing an unauthenticated remote attacker to bypass authentication and access protected upstream resources. Deployments that do not use auth_request-style subrequests or that do not enable --ping-user-agent/--gcp-healthchecks are not affected. This issue is fixed in 7.15.2.
From the CVE record · GitHub_M
OAuth2 Proxy can mistake requests for successful health checks when used with an auth_request-style integration and either --ping-user-agent or --gcp-healthchecks enabled. An unauthenticated remote attacker can send a request with the configured health check User-Agent to access protected upstream resources, regardless of the requested path.
Check deployments using Go package github.com/oauth2-proxy/oauth2-proxy/v7 before 7.15.2 or the unmaintained github.com/oauth2-proxy/oauth2-proxy package through 3.2.0.