Critical · published July 30, 2025
🚨 A crafty crafted URL is all it takes to sidestep authentication in OAuth2-Proxy versions 7.10.0 and below! 🔥 Think of your regex patterns as a bouncer at a club. If he’s not checking IDs closely enough and lets anyone through with a fake ID that looks close enough to the real thing, any partygoer can waltz right in! An attacker could easily bypass authentication and gain unauthorized access to protected resources, exposing sensitive data and compromising the security of your system. This could lead to data breaches or unauthorized actions taken on behalf of legitimate users—definitely not the kind of surprise you want at your next security audit!
Think of your regex patterns as a bouncer at a club. If he’s not checking IDs closely enough and lets anyone through with a fake ID that looks close enough to the real thing, any partygoer can waltz right in! This vulnerability arises from the skip_auth_routes configuration option that allows regex patterns to match against full request URIs, allowing attackers to exploit overly broad patterns. When regex patterns contain wildcards or are not properly anchored, they can inadvertently allow unauthorized requests to pass through.
An attacker could easily bypass authentication and gain unauthorized access to protected resources, exposing sensitive data and compromising the security of your system. This could lead to data breaches or unauthorized actions taken on behalf of legitimate users—definitely not the kind of surprise you want at your next security audit! Upgrade to OAuth2-Proxy version 7.11.0 immediately to close this critical hole. In the meantime, audit your skip_auth_routes configuration for any overly permissive patterns, and replace wildcards with exact matches. Ensure your regex patterns start with ^ and end with $ to avoid any unwanted matches! You've got this! Follow these steps, and you’ll keep your systems safe and sound! 🛡️