Vulnerabilidad · Publicado 25/08/2026
Ech0 versiones hasta 4.5.6 presenta una vulnerabilidad en la validación de redirect_uri OAuth que solo verifica esquema y host, ignorando ruta, parámetros y fragmentos. Esto permite a atacantes redirigir tokens de autenticación a dominios controlados después de pasar la validación inicial. Empresas en LATAM que usan Ech0 para autenticación federada enfrentan riesgo alta de compromiso de sesiones y acceso no autorizado a sistemas integrados.
Ech0 through 4.5.6 contains an OAuth redirect URI validation vulnerability in parseAndValidateClientRedirect (internal/service/auth/auth.go) that compares only the scheme and host of the client-supplied redirect_uri against the admin-configured allowlist, ignoring path, query, and fragment components. The redirect_uri is embedded into the signed state JWT at login time without validation. An attacker can craft a redirect_uri whose host matches an allowed origin but whose path is attacker-influenced; after the OAuth exchange the victim is redirected to that path with a one-time exchange code in the query string. If the code leaks (e.g., via Referer, analytics, or an open redirect on that host), the attacker can trade it at the public POST /api/auth/exchange endpoint for the victim's access and refresh tokens. Fixed in 4.7.3.
Score: 8/10 — Severidad: HIGH — Estado NIST: Received
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
CWE-601
Publicado en NIST NVD.