Is CVE-2014-3120 exploited in the wild?

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

How severe is CVE-2014-3120?

Critical severity, with a CVSS score of 3.1, published 17 May 2022.

Which products and versions are affected?

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

Is there a fix for CVE-2014-3120?

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

How is CVE-2014-3120 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2014-3120?

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-2014-3120: Elasticsearch Improper Access Control vulnerability

CVE-2014-3120 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2022-05-17

The default configuration in Elasticsearch before version 1.2 enables dynamic scripting, allowing remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to _search. This vulnerability is exploited in the wild and is included in CISA's Known Exploited Vulnerabilities catalog.

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

Quick answers

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

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

Affected products

Elasticsearch Elasticsearch before 1.2.0

Identifiers

CVE-2014-3120
GHSA-mrfm-jxgf-2h6v

Timeline

2014-07-28: disclosed: NVD Published Date
2022-03-25: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
2014-05-22: other: Exploit-DB entry published (approximate based on BID/OSVDB timing)

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