CVE-2014-3120
CVE-2014-3120 is a high-severity vulnerability (CVSS 3.1 base score 8.1). Elasticsearch enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code. CISA added it to the Known Exploited Vulnerabilities catalog on 2022-03-25, with a remediation due date of 2022-04-15 for US federal civilian agencies. As of 2026-11-22, EPSS estimates an 88.6% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
- CVSS 3.1
- 8.1 HIGH
- EPSS
- 88.6% (99th pct)
- CISA KEV
- Exploited
- Published
- 2014-07-28
- Weakness
- CWE-284
- Ports
- 9200 Elasticsearch
Elasticsearch Remote Code Execution Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2014-3120
Description
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.
Key Findings
as of 2026-11-22- CISA added CVE-2014-3120 to the KEV catalog 2,797 days after its CVE record was published.
- It is one of 3 Elastic entries in the CISA KEV catalog, and one of 3 added in 2022.
- Its current EPSS score (88.6%) is higher than that of 71% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact partial, 2025-02-10).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| - | - | n/a |
References
8 linksExploits & PoCs
Vulnerability databases
Other references
- https://www.elastic.co/blog/logstash-1-4-3-released
- http://bouk.co/blog/elasticsearch-rce/
- http://www.rapid7.com/db/modules/exploit/multi/elasticsearch/script_mvel_rce
- https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearch
- https://www.elastic.co/community/security/
Record Details
- Publicly disclosed
- 2014-05-15
- Published
- 2014-07-28
- Last updated
- 2025-10-22
- Assigner (CNA)
- mitre
- Credited to
- -
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.