CVE-2021-41192: Insecure default configuration
Redash is a package for data visualization and sharing. If an admin sets up Redash versions 10.0.0 and prior without explicitly specifying the REDASHCOOKIESECRET or REDASHSECRETKEY environment variables, a default value is used for both that is the same across all installations. In such cases, the instance is vulnerable to attackers being able to forge sessions using the known default value. This issue only affects installations where the REDASHCOOKIESECRET or REDASHSECRETKEY environment variables have not been explicitly set. This issue does not affect users of the official Redash cloud images, Redash's Digital Ocean marketplace droplets, or the scripts in the getredash/setup repository. These instances automatically generate unique secret keys during installation. One can verify whether one's instance is affected by checking the value of the REDASHCOOKIESECRET environment variable. If it is c292a0a3aa32397cdb050e233733900f, should follow the steps to secure the instance, outlined in the GitHub Security Advisory.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2021-41192?
CVE-2021-41192 is considered a high-severity vulnerability due to the risk of exposing sensitive data across installations.
How do I fix CVE-2021-41192?
To fix CVE-2021-41192, explicitly set the `REDASH_COOKIE_SECRET` and `REDASH_SECRET_KEY` environment variables in your Redash configuration.
Which versions are affected by CVE-2021-41192?
CVE-2021-41192 affects Redash versions 10.0.0 and prior.
What type of vulnerability is CVE-2021-41192?
CVE-2021-41192 is a security vulnerability related to the improper default configuration of secret keys.
What could happen if CVE-2021-41192 is exploited?
If exploited, CVE-2021-41192 may allow attackers to gain access to other users' sessions and sensitive information.