CVE-2020-36144 Information disclosure in n/a
Attackers can leak information via LDAP injection in Redash due to unsanitized username inputs in search filters.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-36144?
CVE-2020-36144 is a medium-severity vulnerability in n/a, published on 18 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Redash 8.0.0 is affected by LDAP Injection. There is an information leak through the crafting of special queries, escaping the provided template since the username included in the search filter lacks sanitization.
Weakness: CWE-74
Which versions are affected by CVE-2020-36144?
1 open source package ship an affected version, including redash. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
redash Bitnami | From 8.0.0 to 8.0.0 | None |
Products include Redash Redash.
How do I fix CVE-2020-36144?
No fix has been published for CVE-2020-36144 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-36144 being exploited?
There is no known exploitation of CVE-2020-36144 in the wild and no public exploit code.
Other vulnerabilities in n/a
- 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-2021-43780 Server-Side Request Forgery (SSRF) in Redash
- CVE-2026-33213 Redash: Open redirect vulnerability in post-login redirect handling
Sources
Also known as BIT-redash-2020-36144, GHSA-j9jc-frfv-jf2p.