Is CVE-2015-1427 exploited in the wild?

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

How severe is CVE-2015-1427?

Critical severity, with a CVSS score of 9.8, published 14 May 2022.

Which products and versions are affected?

org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=0,fixed=1.3.8.

Is there a fix for CVE-2015-1427?

Yes. org.elasticsearch:elasticsearch (Maven): upgrade to 1.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2015-1427 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2015-1427?

Check whether you run Elasticsearch or org.elasticsearch:elasticsearch (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-2015-1427: Improper Access Control in Elasticsearch

CVE-2015-1427 · Severity: critical · CVSS 9.8 · Exploited in the wild · Published 2022-05-14

The Groovy scripting engine in Elasticsearch allows remote attackers to bypass sandbox protection mechanisms and execute arbitrary shell commands via crafted scripts. This vulnerability stems from insufficient restriction of the Groovy environment, enabling unauthenticated remote code execution.

Technologies: Elasticsearch, org.elasticsearch:elasticsearch (Maven). Vendors: Elastic, Maven.

Quick answers

Is CVE-2015-1427 exploited in the wild?: Yes. CVE-2015-1427 is known to be exploited in the wild, first recorded on 25 March 2022. Treat it as urgent.
How severe is CVE-2015-1427?: Critical severity, with a CVSS score of 9.8, published 14 May 2022.
Which products and versions are affected?: org.elasticsearch:elasticsearch (Maven) ECOSYSTEM:introduced=0,fixed=1.3.8.
Is there a fix for CVE-2015-1427?: Yes. org.elasticsearch:elasticsearch (Maven): upgrade to 1.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2015-1427 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2015-1427?: Check whether you run Elasticsearch or org.elasticsearch:elasticsearch (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.elasticsearch:elasticsearch (Maven): upgrade to 1.3.8 or later

# set org.elasticsearch:elasticsearch to 1.3.8 in your pom.xml or build.gradle

Affected products

Elasticsearch Elasticsearch before 1.3.8, 1.4.x before 1.4.3

Identifiers

CVE-2015-1427
GHSA-w94p-6mhw-4qxw

Timeline

2015-02-11: advisory: Vendor release of Elasticsearch 1.4.3 and 1.3.8 addressing the issue
2022-03-25: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
2022-03-25: disclosed: NVD publication date

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