CVE-2014-3120: Elasticsearch Remote Code Execution Vulnerability

Published Dec 9, 2013
·
Updated

Common Vulnerabilities and Exposures assigned an identifier CVE-2014-3120 to the following vulnerability:

Name: CVE-2014-3120 URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3120 Assigned: 20140429 Reference: EXPLOIT-DB:33370 Reference: http://www.exploit-db.com/exploits/33370 Reference: http://bouk.co/blog/elasticsearch-rce/ Reference: http://www.rapid7.com/db/modules/exploit/multi/elasticsearch/scriptmvelrce Reference: https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearch Reference: http://www.securityfocus.com/bid/67731 Reference: OSVDB:106949 Reference: http://www.osvdb.org/106949

The default configuration in Elasticsearch before 1.2 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine.

As noted in <http://bouk.co/blog/elasticsearch-rce/>, adding "script.disabledynamic: true" to elasticsearch.yml, and ensuring Elasticsearch only binds to localhost, can help mitigate this issue.

Other sources

Elasticsearch enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code.

CISA

It was discovered that the default configuration of Elasticsearch enabled dynamic scripting, allowing a remote attacker to execute arbitrary MVEL expressions and Java code via the source parameter passed to search.

The default configuration in Elasticsearch before 1.4.0.Beta1 enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code via the source parameter to search. NOTE: this only violates the vendor's intended security policy if the user does not run Elasticsearch in its own independent virtual machine.

GitHub

Affected Software

6 affected componentsFixes available
redhat/katello-configure<0:1.4.5.1-3.el6
0:1.4.5.1-3.el6
redhat/elasticsearch<1.2.0
1.2.0
maven/org.elasticsearch:elasticsearch<1.4.0.Beta1
1.4.0.Beta1
Elasticsearch Elasticsearch<=1.1.1
Elastic Elasticsearch
Elastic Elasticsearch<1.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/katello-configure to a version that resolves this vulnerability.

    Fixed in 0:1.4.5.1-3.el6
  2. Upgrade

    Upgrade redhat/elasticsearch to a version that resolves this vulnerability.

    Fixed in 1.2.0
  3. Upgrade

    Upgrade maven/org.elasticsearch:elasticsearch to a version that resolves this vulnerability.

    Fixed in 1.4.0.Beta1
  4. Configuration

    Add `script.disable_dynamic: true` to `elasticsearch.yml` to mitigate CVE-2014-3120 (disables dynamic scripting used for MVEL/Java execution via the `source` parameter to `_search`).

    Elasticsearch script.disable_dynamic = true
  5. Compensating control

    Ensure Elasticsearch only binds to localhost (run it bound to 127.0.0.1) to reduce exposure to remote attackers for CVE-2014-3120.

Event History

Dec 9, 2013
CVE Published
12:00 AM
Jul 28, 2014
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Data Sourced
via NVD·07:55 PM
DescriptionSeverityWeaknessAffected Software
Mar 25, 2022
Known Exploited
via CISA·12:00 AM
May 17, 2022
Advisory Published
via GitHub·03:28 AM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2014-3120?

CVE-2014-3120 has been classified with a severity level that indicates a critical vulnerability in its affected components.

2

How do I fix CVE-2014-3120?

To fix CVE-2014-3120, update the affected packages to the recommended versions specified in the official advisories.

3

Which software is affected by CVE-2014-3120?

CVE-2014-3120 affects the 'katello-configure' package version 1.4.5.1-3.el6, 'elasticsearch' version 1.2.0, and various versions of 'org.elasticsearch:elasticsearch'.

4

Is the vulnerability CVE-2014-3120 publicly disclosed?

Yes, CVE-2014-3120 has been publicly disclosed and documented by various cybersecurity databases and vendors.

5

What are the potential impacts of CVE-2014-3120?

The potential impacts of CVE-2014-3120 include unauthorized access and compromise of data within the affected Elasticsearch instances.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203