Search for packages
| purl | pkg:maven/org.apache.ignite/ignite-core@2.0.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-16c2-gkg9-qbaj
Aliases: CVE-2017-7686 GHSA-8p83-68cw-943f PYSEC-2017-146 |
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. |
Affected by 5 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-8xff-d5ab-bqgf
Aliases: CVE-2018-1295 GHSA-chp4-rv79-68j3 |
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. |
Affected by 3 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-d6hk-e64u-tbcj
Aliases: CVE-2020-1963 GHSA-5wm5-8q42-rhxg |
File system access via H2 in Apache Ignite 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. |
Affected by 1 other vulnerability. |
|
VCID-kxtv-ma18-8fer
Aliases: CVE-2021-28163 GHSA-j6qj-j888-vvgq |
Directory exposure in jetty ### Impact If the `${jetty.base}` directory or the `${jetty.base}/webapps` directory is a symlink (soft link in Linux), the contents of the `${jetty.base}/webapps` directory may be deployed as a static web application, exposing the content of the directory for download. For example, the problem manifests in the following `${jetty.base}`: ```$ tree demo-base/ demo-base/ ├── etc ├── lib ├── resources ├── start.d ├── deploy │ └── async-rest.war └── webapps -> deploy ``` ### Workarounds Do not use a symlink |
Affected by 4 other vulnerabilities. |
|
VCID-s8a4-9j7s-8fc8
Aliases: CVE-2018-1273 GHSA-4fq3-mr56-cg6r |
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. |
Affected by 2 other vulnerabilities. |
|
VCID-ykug-1dhq-tygt
Aliases: CVE-2018-8018 GHSA-qcjv-wfcg-mmpr |
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. |
Affected by 2 other vulnerabilities. Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||