CVE-2021-43777: fallo de gravedad media en getredash redash
Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce)
Publicada el · Actualizada el
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 6.8epss 0.3%
probabilidad de explotación
0.3%top 78% de las CVE
explotación observada
noninguna fuente lo reporta
Redash is a package for data visualization and sharing. In Redash version 10.0 and prior, the implementation of Google Login (via OAuth) incorrectly uses the `state` parameter to pass the next URL to redirect the user to after login. The `state` parameter should be used for a Cross-Site Request Forgery (CSRF) token, not a static and easily predicted value. This vulnerability does not affect users who do not use Google Login for their instance of Redash. A patch in the `master` and `release/10.x.x` branches addresses this by replacing `Flask-Oauthlib` with `Authlib` which automatically provides and validates a CSRF token for the state variable. The new implementation stores the next URL on the user session object. As a workaround, one may disable Google Login to mitigate the vulnerability.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Productos afectados
getredash · redashCVEs relacionadas — getredash redash
En el mismo producto, de las más peligrosas a las menos.
CVE-2021-41192HIGHInsecure default configurationEPSS 8.1%CVE-2021-43780MEDIUMServer-Side Request Forgery (SSRF) in RedashEPSS 1.0%CVE-2026-42093HIGHRedash: SQL Injection via Query Results parameterized query substitutionEPSS 0.7%CVE-2026-77371CRITICALRedash: DuckDB query runner allows arbitrary file read/write via unrestricted external accessEPSS 0.5%CVE-2026-76083MEDIUMRedash: JSON data source query URL can bypass base URL restrictionEPSS 0.4%CVE-2026-33213MEDIUMRedash: Open redirect vulnerability in post-login redirect handlingEPSS 0.3%