# CVE-2021-43780: Server-Side Request Forgery (SSRF) in Redash

> Attackers can exploit SSRF in Redash URL-loading data sources to access internal resources if those sources are 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-fcpv-hgq6-87h7

## What is CVE-2021-43780?

CVE-2021-43780 is a medium-severity server-side request forgery 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 versions 10.0 and priorm the implementation of URL-loading data sources like JSON, CSV, or Excel is vulnerable to advanced methods of Server Side Request Forgery (SSRF). These vulnerabilities are only exploitable on installations where a URL-loading data source is enabled. As of time of publication, the `master` and `release/10.x.x` branches address this by applying the Advocate library for making http requests instead of the requests library directly. Users should upgrade to version 10.0.1 to receive this patch. There are a few workarounds for mitigating the vulnerability without upgrading. One can disable the vulnerable data sources entirely, by adding the following env variable to one's configuration, making them unavailable inside the webapp. One can switch any data source of certain types (viewable in the GitHub Security Advisory) to be `View Only` for all groups on the Settings > Groups > Data Sources screen. For users unable to update an admin may modify Redash's configuration through environment variables to mitigate this issue. Depending on the version of Redash, an admin may also need to run a CLI command to re-encrypt some fields in the database. The `master` and `release/10.x.x` branches as of time of publication have removed the default value for `REDASH_COOKIE_SECRET`. All future releases will also require this to be set explicitly. For existing installations, one will need to ensure that explicit values are set for the `REDASH_COOKIE_SECRET` and `REDASH_SECRET_KEY `variables.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Redash Redash.

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

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

## Is CVE-2021-43780 being exploited?

There is no known exploitation of CVE-2021-43780 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-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-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-43780 and fix it if it is affected.

What it is: CVE-2021-43780 is a medium-severity server-side request forgery 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-43780 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-43780/ (Markdown: https://insights.sbomify.com/CVE-2021-43780/index.md)
```

## Sources

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

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