CVE-2025-54576

{"id": "CVE-2025-54576", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "published": "2025-07-30T20:15:37.677", "references": [{"url": "https://github.com/oauth2-proxy/oauth2-proxy/blob/f4b33b64bd66ad28e9b0d63bea51837b83c00ca1/oauthproxy.go#L582-L584", "source": "security-advisories@github.com"}, {"url": "https://github.com/oauth2-proxy/oauth2-proxy/blob/f4b33b64bd66ad28e9b0d63bea51837b83c00ca1/pkg/requests/util/util.go#L37-L44", "source": "security-advisories@github.com"}, {"url": "https://github.com/oauth2-proxy/oauth2-proxy/commit/9ffafad4b2d2f9f7668e5504565f356a7c047b77", "source": "security-advisories@github.com"}, {"url": "https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.11.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-7rh7-c77v-6434", "source": "security-advisories@github.com"}, {"url": "https://oauth2-proxy.github.io/oauth2-proxy/configuration/overview/#proxy-options", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-290"}]}], "descriptions": [{"lang": "en", "value": "OAuth2-Proxy is an open-source tool that can act as either a standalone reverse proxy or a middleware component integrated into existing reverse proxy or load balancer setups. In versions 7.10.0 and below, oauth2-proxy deployments are vulnerable when using the skip_auth_routes configuration option with regex patterns. Attackers can bypass authentication by crafting URLs with query parameters that satisfy configured regex patterns, allowing unauthorized access to protected resources. The issue stems from skip_auth_routes matching against the full request URI. Deployments using skip_auth_routes with regex patterns containing wildcards or broad matching patterns are most at risk. This issue is fixed in version 7.11.0. Workarounds include: auditing all skip_auth_routes configurations for overly permissive patterns, replacing wildcard patterns with exact path matches where possible, ensuring regex patterns are properly anchored (starting with ^ and ending with $), or implementing custom validation that strips query parameters before regex matching."}, {"lang": "es", "value": "OAuth2-Proxy es una herramienta de c\u00f3digo abierto que puede actuar como proxy inverso independiente o como componente de middleware integrado en configuraciones existentes de proxy inverso o balanceador de carga. En las versiones 7.10.0 y anteriores, las implementaciones de OAuth2-Proxy son vulnerables al usar la opci\u00f3n de configuraci\u00f3n skip_auth_routes con patrones de expresiones regulares. Los atacantes pueden eludir la autenticaci\u00f3n manipulando una URL con par\u00e1metros de consulta que cumplen con los patrones de expresiones regulares configurados, lo que permite el acceso no autorizado a recursos protegidos. El problema se debe a que skip_auth_routes coincide con la URI de solicitud completa. Las implementaciones que utilizan skip_auth_routes con patrones de expresiones regulares que contienen comodines o patrones de coincidencia general son las m\u00e1s vulnerables. Este problema se solucion\u00f3 en la versi\u00f3n 7.11.0. Las soluciones alternativas incluyen: auditar todas las configuraciones de skip_auth_routes para detectar patrones excesivamente permisivos, reemplazar los patrones comod\u00edn con coincidencias de ruta exactas cuando sea posible, garantizar que los patrones de expresiones regulares est\u00e9n correctamente anclados (empezando por ^ y terminando por $) o implementar una validaci\u00f3n personalizada que elimine los par\u00e1metros de consulta antes de la coincidencia con las expresiones regulares."}], "lastModified": "2025-07-31T18:42:37.870", "sourceIdentifier": "security-advisories@github.com"}