dbcve.org
KylinApplication · Apache

CVE-2020-13926

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-14
Fix available
A fix is available. Upgrade to 3.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Kylin concatenates and executes a Hive SQL in Hive CLI or beeline when building a new segment; some part of the HQL is from system configurations, while the configuration can be overwritten by certain rest api, which makes SQL injection attack is possible. Users of all previous versions after 2.0 should upgrade to 3.1.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Kylin has a SQL injection vulnerability where system configurations used in Hive SQL statements during cube segment building can be overwritten via the REST API, allowing arbitrary SQL commands to be executed through Hive CLI or beeline.

MitigationUpgrade to Apache Kylin 3.1.0 or later. As an immediate workaround, restrict access to the Kylin REST API to trusted administrators only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KylinApplication
Affected:>= 2.0.0, < 3.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kylin installation and version
    Locate the Kylin installation directory (typically $KYLIN_HOME) and run the version command: cd $KYLIN_HOME && bin/kylin.sh version. Alternatively, check for a version file in the Kylin home directory.
    Affected if The installed version is Apache Kylin 2.0.0 through 3.0.x (any version >= 2.0.0 but < 3.1.0)
  2. Verify REST API accessibility
    Confirm that the Kylin REST API is accessible over the network. The default port is 7070. Check if the API endpoints respond to HTTP requests from untrusted networks.
    Affected if The Kylin REST API is exposed to untrusted networks or users
  3. Confirm cube building with Hive is configured
    Check if any cubes are configured to use Hive as the source for building cube segments. List existing cubes via the REST API or web UI, and verify the table and storage settings.
    Affected if Cubes are configured to build segments using Hive SQL statements
  4. Inspect custom Hive configurations in Kylin
    Query the Kylin configuration for any custom Hive parameters or overrides that could be modified via the REST API. Check kylin.properties or the result of the /api/admin/config endpoint.
    Affected if Custom Hive configuration parameters exist that could be overwritten
  5. Review recent configuration change logs
    Check Kylin's audit logs or configuration change history to identify any unauthorized or unexpected modifications to Hive-related settings via the REST API.
    Affected if There are recent modifications to system configurations that affect Hive SQL statements

You are affected if Apache Kylin version 2.0.0 through 3.0.x is running and its REST API is accessible to untrusted users while cube building with Hive is configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.0 or later
Fixed in 3.1.0
Interim mitigation

Upgrade to Apache Kylin 3.1.0 or later. As an immediate workaround, restrict access to the Kylin REST API to trusted administrators only.

Recommended fix High confidence

3.1.0

  1. 1. Backup your existing Kylin configuration, metadata, and data directories
  2. 2. Stop the Kylin service gracefully
  3. 3. Download Apache Kylin 3.1.0 from the official Apache downloads page (https://kylin.apache.org/download/)
  4. 4. Install Kylin 3.1.0 on your cluster, ensuring Hadoop, Hive, and HBase dependencies are compatible
  5. 5. Restore your configuration and metadata from the backup
  6. 6. Start the Kylin service
  7. 7. Verify the SQL injection vulnerability is resolved by confirming the REST API no longer allows configuration overwriting that leads to SQL injection
  8. 8. Test cube building and query functionality to ensure normal operations
Caveat Review Kylin 3.1.0 release notes for any configuration or API changes; minor version upgrades may introduce behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kylin Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13926 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-13926 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data