Overview 4 matches · 3 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
3
75.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
25.0%
blocked by ARMR today
3
75.0%
partly blocked
0
0.0%
not blocked
1
25.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
4
100.0%
split by
peak 1 / month
Apr 171
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
May 170
Jun 171
No exploit published1
High1
not blocked1
No public exploit1
Jul 170
Aug 170
Sep 170
Oct 170
Nov 170
Dec 170
Jan 180
Feb 180
Mar 180
Apr 181
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
May 180
Jun 180
Jul 181
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
May 17Jul 17Sep 17Nov 17Jan 18Mar 18May 18Jul 18
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-8018 | Critical | 2018-07-20 | Protected by Waratek | No public exploit | In Apache Ignite before 2.4.8 and 2.5.x before 2.5.3, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to GridClientJdkMarshaller deserialization endpoint. |
| CVE-2018-1295 | Critical | 2018-04-02 | Protected by Waratek | No public exploit | In Apache Ignite 2.3 or earlier, the serialization mechanism does not have a list of classes allowed for serialization/deserialization, which makes it possible to run arbitrary code when 3-rd party vulnerable classes are present in Ignite classpath. The vulnerability can be exploited if the one sends a specially prepared form of a serialized object to one of the deserialization endpoints of some Ignite components - discovery SPI, Ignite persistence, Memcached endpoint, socket steamer. |
| CVE-2017-7686 | High | 2017-06-28 | No exploit published | No public exploit | Apache Ignite 1.0.0-RC3 to 2.0 uses an update notifier component to update the users about new project releases that include additional functionality, bug fixes and performance improvements. To do that the component communicates to an external PHP server (http://ignite.run) where it needs to send some system properties like Apache Ignite or Java version. Some of the properties might contain user sensitive information. |
| CVE-2016-6805 | Medium | 2017-04-07 | Protected by Waratek | No public exploit | Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents. |