Overview 6 matches · 3 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
3
50.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
3
50.0%
blocked by ARMR today
3
50.0%
partly blocked
0
0.0%
not blocked
3
50.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
16.7%
Working exploit published
1
16.7%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
4
66.7%
split by
peak 2 / quarter
Q4 141
No exploit published1
Medium1
not blocked1
No public exploit1
Q1 150
Q2 151
Protected by Waratek1
Medium1
blocked by ARMR today1
Working exploit published1
Q3 151
Protected by Waratek1
Medium1
blocked by ARMR today1
Exploited1
Q4 150
Q1 160
Q2 160
Q3 160
Q4 160
Q1 170
Q2 170
Q3 170
Q4 170
Q1 180
Q2 180
Q3 181
No exploit published1
Medium1
not blocked1
No public exploit1
Q4 182
Protected by Waratek1
No exploit published1
Medium2
blocked by ARMR today1
not blocked1
No public exploit2
Q4 14Q2 15Q4 15Q2 16Q4 16Q2 17Q4 17Q2 18Q4 18
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-17247 | Medium | 2018-12-20 | Protected by Waratek | No public exploit | Elasticsearch Security versions 6.5.0 and 6.5.1 contain an XXE flaw in Machine Learning's find_file_structure API. If a policy allowing external network access has been added to Elasticsearch's Java Security Manager then an attacker could send a specially crafted request capable of leaking content of local files on the Elasticsearch node. This could allow a user to access information that they should not have access to. |
| CVE-2018-17244 | Medium | 2018-12-20 | No exploit published | No public exploit | Elasticsearch Security versions 6.4.0 to 6.4.2 contain an error in the way request headers are applied to requests when using the Active Directory, LDAP, Native, or File realms. A request may receive headers intended for another request if the same username is being authenticated concurrently; when used with run as, this can result in the request running as the incorrect user. This could allow a user to access information that they should not have access to. |
| CVE-2018-3824 | Medium | 2018-09-19 | No exploit published | No public exploit | X-Pack Machine Learning versions before 6.2.4 and 5.6.9 had a cross-site scripting (XSS) vulnerability. If an attacker is able to inject data into an index that has a ML job running against it, then when another user views the results of the ML job it could allow the attacker to obtain sensitive information from or perform destructive actions on behalf of that other ML user. |
| 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-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. |