Overview 108 matches · 53 in Waratek scope · 6 protected · 3 exploited · 2 CISA KEV · 8 public PoC · 5 EPSS ≥ 0.5
108matches
53in Waratek scope49.1%
6protected5.6%
3exploited2.8%
2CISA KEV1.9%
8public PoC7.4%
5EPSS ≥ 0.54.6%
Protected by Waratek
6
5.6%
Rule in development
0
0.0%
Mitigation candidate
2
1.9%
No exploit published
45
41.7%
Outside Waratek scope
0
0.0%
Not applicable
55
50.9%
Withdrawn CVE
0
0.0%
blocked by ARMR today
6
5.6%
partly blocked
0
0.0%
not blocked
102
94.4%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 49 / year
20142
Protected by Waratek1
No exploit published1
High1
Medium1
blocked by ARMR today1
not blocked1
Exploited1
No public exploit1
20153
Protected by Waratek3
Critical1
Medium2
blocked by ARMR today3
Exploited2
Working exploit published1
20160
20171
No exploit published1
High1
not blocked1
No public exploit1
20187
Protected by Waratek1
No exploit published3
Not applicable3
Critical1
High1
Medium5
blocked by ARMR today1
not blocked6
No public exploit7
20194
No exploit published2
Not applicable2
High2
Medium2
not blocked4
No public exploit4
20204
No exploit published4
High2
Medium1
Low1
not blocked4
No public exploit4
20219
Mitigation candidate1
No exploit published7
Not applicable1
High1
Medium8
not blocked9
Working exploit published2
No public exploit7
20225
No exploit published5
High2
Medium3
not blocked5
No public exploit5
20236
Protected by Waratek1
Mitigation candidate1
No exploit published3
Not applicable1
High5
Medium1
blocked by ARMR today1
not blocked5
Proof of concept only1
No public exploit5
20249
No exploit published8
Not applicable1
High3
Medium6
not blocked9
No public exploit9
20259
No exploit published8
Not applicable1
High4
Medium5
not blocked9
Working exploit published1
No public exploit8
202649
No exploit published3
Not applicable46
High6
Medium43
not blocked49
No public exploit49
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-3823 | Medium | 2018-09-19 | Not applicable | No public exploit | X-Pack Machine Learning versions before 6.2.4 and 5.6.9 had a cross-site scripting (XSS) vulnerability. Users with manage_ml permissions could create jobs containing malicious data as part of their configuration that could allow the attacker to obtain sensitive information from or perform destructive actions on behalf of other ML users viewing the results of the jobs. |
| CVE-2015-5377 | Critical | 2018-03-06 | Not applicable | No public exploit | Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the transport protocol. NOTE: ZDI appears to claim that CVE-2015-3253 and CVE-2015-5377 are the same vulnerability |
| CVE-2015-4165 | High | 2017-08-09 | No exploit published | No public exploit | 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 Elasticsearch is running can write to a location that the other application can read and execute from, allows remote authenticated users to write to and create arbitrary snapshot metadata files, and potentially execute arbitrary code. |
| 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-3337 | Medium | 2015-05-01 | Protected by Waratek | Working exploit published | 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. |
| 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-6439 | Medium | 2014-10-10 | No exploit published | No public exploit | 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. |
| 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. |