# 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.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g8xr-f424-h2rv

## 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 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2021-41192?

It affects 1 product.


Products: 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:

- Redash Setup Configuration - Default Secrets Disclosure (nuclei): http/cves/2021/CVE-2021-41192.yaml

## Other vulnerabilities in getredash redash

- [CVE-2020-12725](https://insights.sbomify.com/CVE-2020-12725/): Server-side request forgery in n/a (high 7.2)
- [CVE-2021-43777](https://insights.sbomify.com/CVE-2021-43777/): Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce) (medium 6.8)
- [CVE-2021-43780](https://insights.sbomify.com/CVE-2021-43780/): Server-Side Request Forgery (SSRF) in Redash (medium 6.8)
- [CVE-2026-33213](https://insights.sbomify.com/CVE-2026-33213/): Redash: Open redirect vulnerability in post-login redirect handling (medium 6.1)
- [CVE-2020-36144](https://insights.sbomify.com/CVE-2020-36144/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41192 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-41192 exists.

Affected product: getredash redash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-41192/ (Markdown: https://insights.sbomify.com/CVE-2021-41192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41192
- OSV: https://osv.dev/vulnerability/CVE-2021-41192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-41192/
Summaries are generated and may contain mistakes; the official description above is the record.