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

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-redash-2020-36144, GHSA-j9jc-frfv-jf2p

## 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 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2020-36144?

1 open source package ship an affected version, including redash. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redash` | Bitnami | From 8.0.0 to 8.0.0 | None |

Products: 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](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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36144 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2020-36144 in the wild and no public exploit code.

Affected packages and fixed versions:
- redash (Bitnami): affected from 8.0.0 up to 8.0.0; no fix listed

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

## Sources

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

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