# CVE-2020-1937: SQL Injection in Kylin

> Attackers can execute malicious database queries via SQL injection in Apache Kylin RESTful APIs, potentially compromising data integrity and confidentiality.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7hmh-8gwv-mfvq

## What is CVE-2020-1937?

CVE-2020-1937 is a high-severity SQL injection vulnerability in Apache Kylin, published on 24 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kylin has some restful apis which will concatenate SQLs with the user input string, a user is likely to be able to run malicious database queries.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

4 open source packages ship an affected version, including org.apache.kylin:kylin-server-base. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.kylin:kylin-server-base` | Maven | All versions | 2.6.5 |
| `org.apache.kylin:kylin-server-base` | Maven | All versions | 2.6.5 |
| `org.apache.kylin:kylin-server-base` | Maven | From 3.0.0 | 3.0.1 |
| `org.apache.kylin:kylin-server-base` | Maven | From 3.0.0 | 3.0.1 |

Products: Apache Kylin.

## How do I fix CVE-2020-1937?

Upgrade org.apache.kylin:kylin-server-base to a fixed version for your release line: 2.6.5 or 3.0.1.

## Is CVE-2020-1937 being exploited?

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

Public exploit code:

- CVE-2020-1937 (github_poc): https://github.com/shanika04/apache_kylin

## Other vulnerabilities in Apache Kylin

- [CVE-2020-1956](https://insights.sbomify.com/CVE-2020-1956/): Apache Kylin OS Command Injection (high 8.8, exploited in the wild)
- [CVE-2026-62390](https://insights.sbomify.com/CVE-2026-62390/): Apache Kylin: SQL Injection Vulnerability in Catalog Cache Refresh API (critical 9.8)
- [CVE-2022-44621](https://insights.sbomify.com/CVE-2022-44621/): Apache Kylin: Command injection by Diagnosis Controller (critical 9.8)
- [CVE-2022-24697](https://insights.sbomify.com/CVE-2022-24697/): Apache Kylin vulnerable to remote code execution (critical 9.8)
- [CVE-2021-31522](https://insights.sbomify.com/CVE-2021-31522/): Apache Kylin unsafe class loading (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-1937 is a high-severity SQL injection vulnerability in Apache Kylin, published on 24 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1937 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.kylin:kylin-server-base (Maven): affected all versions; fixed in 2.6.5
- org.apache.kylin:kylin-server-base (Maven): affected all versions; fixed in 2.6.5
- org.apache.kylin:kylin-server-base (Maven): affected from 3.0.0; fixed in 3.0.1
- org.apache.kylin:kylin-server-base (Maven): affected from 3.0.0; fixed in 3.0.1

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

## Sources

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

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