Ignite vulnerabilitiesAnd the versions its exploited flaws hit.
Ignite is made by Apache. We track 7 published vulnerabilities in it, across 44 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 March 2022. If you run Ignite, check your version against the exploited flaws below and patch those first.
The most recent Ignite flaw added to the known-exploited list is CVE-2018-1273, on 25 March 2022. We keep watching the known-exploited list.
Which versions of Ignite do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2018-1273Exploited list, 25 Mar 2022
VMware Tanzu Spring Data Commons Property Binder Vulnerability
1.0.0-rc31.0.01.0.1 to 2.5.0
Which Ignite vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8VMware Tanzu Spring Data Commons Property Binder Vulnerability
Spring Data Commons contains a property binder vulnerability which can allow an attacker to perform remote code execution.
Which Ignite flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 97%
Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements.
- 6.7%CVE-2018-8018Critical
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...
- 6.3%CVE-2018-1295Critical
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...
- 5.0%CVE-2020-1963Critical
Apache Ignite uses H2 database to build SQL distributed execution engine.
- 4.2%
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,...
- 3.0%CVE-2017-7686High
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.
- 2.0%CVE-2016-6805Medium
Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents.
- 0.5%CVE-2025-48977High
Relative Path Traversal vulnerability in Apache Ignite REST API.
Running Ignite? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Spring Data Commons contains a property binder vulnerability which can allow an attacker to perform remote code execution.
- Matched to
- Ignite on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Ignite, across 44 versions. The most recent Ignite flaw added to the known-exploited list is CVE-2018-1273, on 25 March 2022.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2018-1273.
Each flaw names its own versions, usually as ranges. The newest, CVE-2018-1273, affects 1.0.0-rc3, 1.0.0, 1.0.1 to 2.5.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Ignite. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.