Threats / Elastic / CVE-2014-3120
CVE-2014-3120
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Elastic Elasticsearch vulnerability
Elasticsearch enabled dynamic scripting by default, allowing remote attackers to execute arbitrary MVEL expressions and Java code without authentication, leading to complete system compromise.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can execute arbitrary code on vulnerable Elasticsearch instances through dynamic script evaluation. This vulnerability has been actively exploited in the wild and requires immediate patching or configuration changes to disable dynamic scripting.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
113 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25).
Probability (EPSS)
EPSS 0.88559 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Elastic, Elasticsearch. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-284 Improper Access Control — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious script payload in MVEL or Java and send it to the Elasticsearch API endpoint.
Business
The organization's Elasticsearch cluster becomes a pivot point for attackers to access sensitive indexed data and internal systems.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary code with the privileges of the Elasticsearch process to establish persistence and lateral movement.
Business
Attackers gain sustained access to infrastructure, enabling data exfiltration, encryption for ransom, or deployment of additional malware.
3
Lateral reach — past segmentation narrative 3
Attacker
I enumerate and extract all indexed data, including credentials, personal information, and business intelligence stored in the cluster.
Business
Confidential data breaches result in regulatory fines, reputational damage, and loss of customer trust.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05