# CVE-2021-43777: Vulnerability in Redash OAuth2 flows due to misuse of state field (should be a nonce)

> Attackers can exploit improper OAuth state handling to redirect users to malicious sites, potentially leading to account takeover if Google Login is enabled.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/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-vhc7-w7r8-8m34

## What is CVE-2021-43777?

CVE-2021-43777 is a medium-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. 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.

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Redash Redash.

## How do I fix CVE-2021-43777?

No fix has been published for CVE-2021-43777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-43777 being exploited?

There is no known exploitation of CVE-2021-43777 in the wild and no public exploit code.

## Other vulnerabilities in getredash redash

- [CVE-2021-41192](https://insights.sbomify.com/CVE-2021-41192/): Insecure default configuration (high 8.1)
- [CVE-2020-12725](https://insights.sbomify.com/CVE-2020-12725/): Server-side request forgery in n/a (high 7.2)
- [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-43777 and fix it if it is affected.

What it is: CVE-2021-43777 is a medium-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: There is no known exploitation of CVE-2021-43777 in the wild and no public exploit code.

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-43777/ (Markdown: https://insights.sbomify.com/CVE-2021-43777/index.md)
```

## Sources

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

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