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.
- 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-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
Which versions are affected by CVE-2021-43780?
It affects 1 product.
Products include 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.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
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 Insecure default configuration
- 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-2026-33213 Redash: Open redirect vulnerability in post-login redirect handling
- CVE-2020-36144 Information disclosure in n/a
Sources
Also known as GHSA-fcpv-hgq6-87h7.