Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2020-1956

Apache Kylin OS Command Injection Vulnerability

Apache Kylin

Apache Kylin 2.3.0, and releases up to 2.6.5 and 3.0.1 has some restful apis which will concatenate os command with the user input string, a user is likely to be able to execute any os command without any protection or validation.

CVSS
8.8
HIGH
EPSS
98%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
22 May 2020
CWE-78

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 25 March 2022. US federal agencies were required to remediate it by 15 April 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 98%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

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

Frequently asked questions

Is CVE-2020-1956 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2020-1956.

What does CVE-2020-1956 affect?

CVE-2020-1956 affects Apache Kylin. Apache Kylin 2.3.0, and releases up to 2.6.5 and 3.0.1 has some restful apis which will concatenate os command with the user input string, a user is likely to be able to execute any os command without any protection or validation.

How severe is CVE-2020-1956?

CVE-2020-1956 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 98%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 April 2022.

How should organisations respond to CVE-2020-1956?

Apply the vendor patch for Apache Kylin as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.