# CVE-2020-13937: Authentication bypass in Apache Kylin > Unauthenticated REST API exposes sensitive configuration data in Apache Kylin, allowing attackers to read confidential information. - **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:** Yes - **Published:** 19 Oct 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-2hpg-vwqj-6h6w ## What is CVE-2020-13937? CVE-2020-13937 is a medium-severity vulnerability in Apache Kylin, published on 19 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Apache Kylin 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.3.1, 2.3.2, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.5.2, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.6.6, 3.0.0-alpha, 3.0.0-alpha2, 3.0.0-beta, 3.0.0, 3.0.1, 3.0.2, 3.1.0, 4.0.0-alpha has one restful api which exposed Kylin's configuration information without any authentication, so it is dangerous because some confidential information entries will be disclosed to everyone. Weakness: CWE-922 (Insecure Storage of Sensitive Information) ## Which versions are affected by CVE-2020-13937? 4 open source packages ship an affected version, including org.apache.kylin:kylin. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.kylin:kylin` | Maven | All versions | 3.1.1 | | `org.apache.kylin:kylin` | Maven | All versions | 3.1.1 | | `org.apache.kylin:kylin` | Maven | From 4.0.0-alpha | 4.0.0-beta | | `org.apache.kylin:kylin` | Maven | From 4.0.0-alpha | 4.0.0-beta | Products: Apache Kylin. ## How do I fix CVE-2020-13937? Upgrade org.apache.kylin:kylin to a fixed version for your release line: 3.1.1 or 4.0.0-beta. ## Is CVE-2020-13937 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-13937 exists. Public exploit code: - Apache Kylin API未授权访问漏洞;CVE-2020-13937;Apache Kylin漏洞 (github_poc): https://github.com/yaunsky/CVE-2020-13937 - Apache Kylin API Unauthorized Access (github_poc): https://github.com/Al1ex/CVE-2020-13937 - Apache Kylin有一个restful api会在没有任何认证的情况下暴露配置信息 (github_poc): https://github.com/kailing0220/CVE-2020-13937 - Apache Kylin - Exposed Configuration File (nuclei): http/cves/2020/CVE-2020-13937.yaml ## 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-13937 and fix it if it is affected. What it is: CVE-2020-13937 is a medium-severity vulnerability in Apache Kylin, published on 19 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-13937 exists. Affected packages and fixed versions: - org.apache.kylin:kylin (Maven): affected all versions; fixed in 3.1.1 - org.apache.kylin:kylin (Maven): affected all versions; fixed in 3.1.1 - org.apache.kylin:kylin (Maven): affected from 4.0.0-alpha; fixed in 4.0.0-beta - org.apache.kylin:kylin (Maven): affected from 4.0.0-alpha; fixed in 4.0.0-beta 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-13937/ (Markdown: https://insights.sbomify.com/CVE-2020-13937/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13937 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13937 - OSV: https://osv.dev/vulnerability/CVE-2020-13937 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-13937/ Summaries are generated and may contain mistakes; the official description above is the record.