ignite: Possible Execution of Arbitrary Code Within Deserialization Endpoints
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Ignite | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Fuse Intergration Services 2.0 based on Fuse 6.3 R7 | |||
| ignite-core | cpe:/a:redhat:jboss_fuse:6.3 | RHSA-2018:2405 | 2018-08-14T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0580 | 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. |
Github GHSA |
GHSA-chp4-rv79-68j3 | Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 6.3% (6.349% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.