Exploited Elasticsearch CVEs
3 CVEs, 3 protected by Waratek
Overview 3 matches · 2 CISA KEV
3matches
2CISA KEV66.7%
Protected by Waratek
3
100.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
blocked by ARMR today
3
100.0%
partly blocked
0
0.0%
not blocked
0
0.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
100.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 1 / month
Jul 141
Protected by Waratek1
High1
blocked by ARMR today1
Exploited1
Aug 140
Sep 140
Oct 140
Nov 140
Dec 140
Jan 150
Feb 151
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Mar 150
Apr 150
May 150
Jun 150
Jul 150
Aug 151
Protected by Waratek1
Medium1
blocked by ARMR today1
Exploited1
Aug 14Oct 14Dec 14Feb 15Apr 15Jun 15Aug 15
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2015-5531 | Medium | 2015-08-17 | Protected by Waratek | Exploited | Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unspecified vectors related to snapshot API calls. |
| CVE-2015-1427 | Critical | 2015-02-17 | Protected by Waratek | Exploited | The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script. |
| CVE-2014-3120 | High | 2014-07-28 | Protected by Waratek | Exploited | 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. |