Skip to content
CTI Academy Sponsor CTI Academy
CRITICAL · CVSS 9.8 CISA Known Exploited Vulnerability

CVE-2015-1427

Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability

Elastic Elasticsearch

The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script.

CVSS
9.8
CRITICAL
EPSS
99.9%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
17 Feb 2015
NVD

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 99.9%, 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:N/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2015-1427 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2015-1427.

What does CVE-2015-1427 affect?

CVE-2015-1427 affects Elastic Elasticsearch. The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script.

How severe is CVE-2015-1427?

CVE-2015-1427 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 99.9%, 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-2015-1427?

Apply the vendor patch for Elastic Elasticsearch 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.