Is CVE-2020-1956 exploited in the wild?

Yes. CVE-2020-1956 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.

How severe is CVE-2020-1956?

Critical severity, with a CVSS score of 3.1, published 27 July 2020.

Which products and versions are affected?

org.apache.kylin:kylin-core-common (Maven) ECOSYSTEM:introduced=0,fixed=2.6.6.

Is there a fix for CVE-2020-1956?

Yes. org.apache.kylin:kylin-core-common (Maven): upgrade to 2.6.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-1956 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2020-1956?

Check whether you run Apache Kylin or org.apache.kylin:kylin-core-common (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-1956: Command Injection in Kylin

CVE-2020-1956 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2020-07-27

Apache Kylin contains an OS command injection vulnerability in its RESTful APIs. The vulnerability occurs because user input is concatenated directly into OS commands without proper validation, allowing an authenticated attacker to execute arbitrary commands on the underlying system.

Technologies: Apache Kylin, org.apache.kylin:kylin-core-common (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2020-1956 exploited in the wild?: Yes. CVE-2020-1956 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.
How severe is CVE-2020-1956?: Critical severity, with a CVSS score of 3.1, published 27 July 2020.
Which products and versions are affected?: org.apache.kylin:kylin-core-common (Maven) ECOSYSTEM:introduced=0,fixed=2.6.6.
Is there a fix for CVE-2020-1956?: Yes. org.apache.kylin:kylin-core-common (Maven): upgrade to 2.6.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-1956 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2020-1956?: Check whether you run Apache Kylin or org.apache.kylin:kylin-core-common (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.kylin:kylin-core-common (Maven): upgrade to 2.6.6 or later

# set org.apache.kylin:kylin-core-common to 2.6.6 in your pom.xml or build.gradle

Affected products

Apache Kylin 2.3.0 to 2.6.5, 3.0.0 to 3.0.1

Identifiers

CVE-2020-1956
GHSA-gprm-xqrc-c2j3

Timeline

2020-07-14: disclosed: Initial public disclosure via oss-security mailing list
2022-03-25: kev added: Added to CISA's Known Exploited Vulnerabilities Catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.