Apache Software Foundation Ignite 1.3.3

CPE Details

Apache Software Foundation Ignite 1.3.3
apache
ignite
1.3.3
2018-10-04
15h01 +00:00
2018-10-04
15h01 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:apache:ignite:1.3.3:*:*:*:*:*:*:*

Informations

Vendor

apache

Product

ignite

Version

1.3.3

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2021-28163 2021-04-01 12h20 +00:00 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.
2.7
Low
CVE-2020-1963 2020-06-03 10h53 +00:00 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.
9.1
Critical
CVE-2018-8018 2018-07-19 18h00 +00:00 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.
9.8
Critical
CVE-2018-1273 2018-04-11 13h00 +00:00 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. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack.
9.8
Critical
CVE-2018-1295 2018-04-02 17h00 +00:00 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.
9.8
Critical
CVE-2016-6805 2017-04-07 17h00 +00:00 Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents.
5.9
Medium