WaratekVRT Sign in

Ignite CVEs with no public exploit

8 CVEs, 5 protected by Waratek

Reset
More filters (1)
Columns
Product ignite✕
Overview 8 matches · 5 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
8matches 5protected62.5% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 5 62.5% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 3 37.5%
Critical 4 50.0% High 2 25.0% Medium 1 12.5% Low 1 12.5% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 5 62.5% partly blocked 0 0.0% not blocked 3 37.5% 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 8 100.0%
split by peak 2 / year
No exploit published: 3Protected by Waratek: 5 Low: 1Medium: 1High: 2Critical: 4 not blocked: 3blocked by ARMR today: 5 No public exploit: 8
20172 Protected by Waratek1 No exploit published1 High1 Medium1 blocked by ARMR today1 not blocked1 No public exploit2 20182 Protected by Waratek2 Critical2 blocked by ARMR today2 No public exploit2 20190 20201 No exploit published1 Critical1 not blocked1 No public exploit1 20211 No exploit published1 Low1 not blocked1 No public exploit1 20220 20230 20240 20251 Protected by Waratek1 Critical1 blocked by ARMR today1 No public exploit1 20261 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1
2017201820192020202120222023202420252026
8 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2025-48977 High 2026-05-28 Protected by Waratek No public exploit Relative Path Traversal vulnerability in Apache Ignite REST API. Authenticated REST API users can read any file on the server with "cmd=log" command and a log path crafted in a certain way. This issue affects Apache Ignite: from 2.0.0 through 2.17.0. Users are recommended to upgrade to version 2.18.0, which fixes the issue.
CVE-2024-52577 Critical 2025-02-14 Protected by Waratek No public exploit In Apache Ignite versions from 2.6.0 and before 2.17.0, configured Class Serialization Filters are ignored for some Ignite endpoints. The vulnerability could be exploited if an attacker manually crafts an Ignite message containing a vulnerable object whose class is present in the Ignite server classpath and sends it to Ignite server endpoints. Deserialization of such a message by the Ignite server may result in the execution of arbitrary code on the Apache Ignite server side.
CVE-2021-28163 Low 2021-04-01 No exploit published No public exploit In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink, the contents of the webapps directory is deployed as a static webapp, inadvertently serving the webapps themselves and anything else that might be in that directory.
CVE-2020-1963 Critical 2020-06-03 No exploit published No public exploit Apache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem.
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.