Elasticsearch vulnerabilities1 known to be exploited.
Elasticsearch has 15 published vulnerabilities across 10 products in our catalogue. 1 of them is on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Elasticsearch, with 5. If you run Elasticsearch software, patch the exploited flaws first.
The most recent Elasticsearch flaw added to the known-exploited list is CVE-2014-3120, on 25 March 2022. We keep watching the known-exploited list.
Which Elasticsearch products have the most vulnerabilities?
Elasticsearch leads with 5 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Elasticsearch vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 8.1Elasticsearch Remote Code Execution Vulnerability
Elasticsearch enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code.
Which Elasticsearch flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 95%CVE-2015-5531Medium
Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unspecified vectors related to snapshot API calls.
- 89%
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.
- 33%CVE-2015-3337Medium
Directory traversal vulnerability in Elasticsearch before 1.4.5 and 1.5.x before 1.5.2, when a site plugin is enabled, allows remote attackers to read arbitrary files via unspecified vectors.
- 4.5%CVE-2015-4165High
The snapshot API in Elasticsearch before 1.6.0 when another application exists on the system that can read Lucene files and execute code from them, is accessible by the attacker, and the Java VM on which...
- 2.5%CVE-2015-5378High
Logstash 1.5.x before 1.5.3 and 1.4.x before 1.4.4 allows remote attackers to read communications between Logstash Forwarder agent and Logstash server.
- 2.0%CVE-2014-6439Medium
Cross-site scripting (XSS) vulnerability in the CORS functionality in Elasticsearch before 1.4.0.Beta1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
- 1.4%CVE-2017-11480High
Packetbeat versions prior to 5.6.4 are affected by a denial of service flaw in the PostgreSQL protocol handler.
- 1.2%CVE-2020-7017Medium
In Kibana versions before 6.8.11 and 7.8.1 the region map visualization in contains a stored XSS flaw.
- 1.2%CVE-2015-5619Medium
Logstash 1.4.x before 1.4.5 and 1.5.x before 1.5.4 with Lumberjack output or the Logstash forwarder does not validate SSL/TLS certificates from the Logstash server, which might allow attackers to obtain sensitive...
- 1.1%CVE-2016-10362Medium
Prior to Logstash version 5.0.1, Elasticsearch Output plugin when updating connections after sniffing, would log to file HTTP basic auth credentials.
All Elasticsearch products we track.
10 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
- Elasticsearchelasticsearch5 vulnerabilities11 versions
- Kibanakibana3 vulnerabilities283 versions
- Logstashlogstash3 vulnerabilities51 versions
- Cloud Enterprisecloud_enterprise1 vulnerability2 versions
- Output Pluginoutput_plugin1 vulnerability2 versions
- Packetbeatpacketbeat1 vulnerability109 versions
- X-Packx-pack1 vulnerability1 version
- X-Pack Reportingx-pack_reporting1 vulnerability1 version
- Csv Output Plugincsv_output_plugin0 vulnerabilities1 version
- Netflow Codec Pluginnetflow_codec_plugin0 vulnerabilities1 version
Running Elasticsearch? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Elasticsearch enables dynamic scripting, which allows remote attackers to execute arbitrary MVEL expressions and Java code.
- Matched to
- Elasticsearch on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 15 published vulnerabilities across 10 products and 462 versions from Elasticsearch. The most recent Elasticsearch flaw added to the known-exploited list is CVE-2014-3120, on 25 March 2022.
1 Elasticsearch vulnerability is on the list of flaws known to be exploited. The most recently added is CVE-2014-3120. The full list is on this page.
Elasticsearch, with 5 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Elasticsearch products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.