CVE-2021-41192 Insecure default configuration
Attackers can forge sessions and take over accounts if Redash admins fail to set unique secret keys, relying on a known default value.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2021-41192?
CVE-2021-41192 is a high-severity vulnerability in getredash redash, published on 23 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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 `REDASH_COOKIE_SECRET` or `REDASH_SECRET_KEY` 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 `REDASH_COOKIE_SECRET or REDASH_SECRET_KEY` 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 `REDASH_COOKIE_SECRET` environment variable. If it is `c292a0a3aa32397cdb050e233733900f`, should follow the steps to secure the instance, outlined in the GitHub Security Advisory.
Weakness: CWE-1188
Which versions are affected by CVE-2021-41192?
It affects 1 product.
Products include Redash Redash.
How do I fix CVE-2021-41192?
No fix has been published for CVE-2021-41192 yet. Limit exposure of the affected software until one is available.
Is CVE-2021-41192 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-41192 exists.
Public exploit code: 1 Nuclei template.
Other vulnerabilities in getredash redash
- CVE-2020-12725 Server-side request forgery in n/a
- CVE-2021-43777 Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce)
- CVE-2021-43780 Server-Side Request Forgery (SSRF) in Redash
- CVE-2026-33213 Redash: Open redirect vulnerability in post-login redirect handling
- CVE-2020-36144 Information disclosure in n/a
Sources
Also known as GHSA-g8xr-f424-h2rv.