CVE-2014-3120
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering.
- In the wild
- CISA lists this as exploited in real attacks. Treat as urgent.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- 2022-03-25 Exploited in the wildAdded to CISA's Known Exploited Vulnerabilities list
- 2022-04-15 Remediation deadlineCISA's due date for federal agencies to fix it
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: yes, CISA lists it. This puts it above everything that is not.
- Exploit odds: 88.6% in the next 30 days (EPSS).
- Severity: 8.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Added to CISA KEV
- 2022-03-25
- Exploit probability
- 88.6% · EPSS, next 30 days
- Weakness
- CWE-284 · Improper access control
- Record status
- Analyzed
Affected
- Elastic Elasticsearch < 1.2.0
Attack profile CVSS 3.1 · 8.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2014-3120.md and follow it. Check whether this project is affected by CVE-2014-3120. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://www.elastic.co/blog/logstash-1-4-3-released
- https://www.elastic.co/community/security/
- https://www.elastic.co/blog/logstash-1-4-3-released
- https://www.elastic.co/community/security/
References
- http://bouk.co/blog/elasticsearch-rce/
- http://www.exploit-db.com/exploits/33370
- http://www.osvdb.org/106949
- http://www.rapid7.com/db/modules/exploit/multi/elasticsearch/script_mvel_rce
- http://www.securityfocus.com/bid/67731
- https://www.elastic.co/blog/logstash-1-4-3-released
- https://www.elastic.co/community/security/
- https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearch
- http://bouk.co/blog/elasticsearch-rce/
- http://www.exploit-db.com/exploits/33370
- http://www.osvdb.org/106949
- http://www.rapid7.com/db/modules/exploit/multi/elasticsearch/script_mvel_rce
- http://www.securityfocus.com/bid/67731
- https://www.elastic.co/blog/logstash-1-4-3-released
- https://www.elastic.co/community/security/
- https://www.found.no/foundation/elasticsearch-security/#staying-safe-while-developing-with-elasticsearch
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2014-3120