Skip to main content
Mallory
HighVulnerability

CVE-2020-1937: SQL Injection in Apache Kylin RESTful APIs

Published Feb 24, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS3.1%88th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2020-1937CWE-89 · Improper Neutralization of Special…

CVE-2020-1937 is a SQL injection vulnerability in Apache Kylin. Certain RESTful API endpoints construct SQL statements by concatenating user-supplied input into database queries without sufficient sanitization or parameterization. This unsafe query construction can allow an attacker to inject malicious SQL through API requests and cause the backend to execute unintended database queries.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow unauthorized execution of arbitrary database queries through vulnerable Apache Kylin RESTful APIs. Depending on the database permissions available to the application, this can result in unauthorized access to data, modification or deletion of records, and other impacts associated with database compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to vulnerable Apache Kylin RESTful APIs to trusted administrators and internal networks only, enforce strong authentication and authorization on exposed endpoints, and place the service behind network access controls or a reverse proxy/WAF capable of detecting SQL injection patterns. Review database permissions used by Kylin and apply least privilege to limit the impact of injected queries. These are compensating controls; upgrading remains the primary fix.

Remediation

Patch, then assume compromise.

Upgrade Apache Kylin to a fixed release. For affected versions prior to 2.6.5, upgrade to 2.6.5 or later. For the 3.0.0 branch, upgrade to 3.0.1 or later.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationKylinapplication
FAQ

Frequently asked questions

Is CVE-2020-1937 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2020-1937 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2020-1937?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2020-1937.
Is there a patch for CVE-2020-1937?
Upgrade Apache Kylin to a fixed release. For affected versions prior to 2.6.5, upgrade to 2.6.5 or later.
What products are affected by CVE-2020-1937?
Apache Software Foundation Kylin.
How severe is CVE-2020-1937?
CVE-2020-1937 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 3.1% (88th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.