{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.ignite:ignite-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1295 in the wild and no public exploit code.","fix":"Upgrade org.apache.ignite:ignite-core to 2.4 or later.","what":"CVE-2018-1295 is a critical unsafe deserialization vulnerability in Apache Ignite, published on 2 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1295 and fix it if it is affected.\n\nWhat it is: CVE-2018-1295 is a critical unsafe deserialization vulnerability in Apache Ignite, published on 2 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1295 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 2.4\n- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 2.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-1295/ (Markdown: https://insights.sbomify.com/CVE-2018-1295/index.md)","id":"CVE-2018-1295","markdown":"https://insights.sbomify.com/CVE-2018-1295/index.md","name":"CVE-2018-1295","record":{"aliases":["GHSA-chp4-rv79-68j3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Ignite","requires_auth":"none","summary":"Attackers can execute arbitrary code by sending malicious serialized objects to Apache Ignite endpoints due to missing class whitelisting.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ignite","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization","id":"CVE-2018-1295","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"deserialization","year":"2018"},"n_packages":2,"n_references":3,"next":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Hadoop","id":"CVE-2018-1296"},"packages":[{"ecosystem":"Maven","fixed":["2.4"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":null,"source":"GHSA-chp4-rv79-68j3"},{"ecosystem":"Maven","fixed":["2.4"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":"pkg:maven/org.apache.ignite/ignite-core","source":"GHSA-chp4-rv79-68j3"}],"prev":{"headline":"Improper Input Validation Apache Commons Email","id":"CVE-2018-1294"},"products":["Apache Ignite"],"published":"2018-04-02","related":[{"cvss_score":9.8,"headline":"VMware Tanzu Spring Data Commons Property Binder","id":"CVE-2018-1273","kev_date_added":"2022-03-25","published":"2018-04-11"},{"cvss_score":9.8,"headline":"Code execution via deserialization in org.apache.ignite:ignite-core","id":"CVE-2018-8018","kev_date_added":null,"published":"2018-07-19"},{"cvss_score":9.5,"headline":"Apache Ignite: Possible RCE when deserializing incoming messages by the server node","id":"CVE-2024-52577","kev_date_added":null,"published":"2025-02-14"},{"cvss_score":9.1,"headline":"File system access via H2 in Apache Ignite","id":"CVE-2020-1963","kev_date_added":null,"published":"2020-06-03"},{"cvss_score":8.5,"headline":"Apache Ignite: REST HTTP arbitrary file read vulnerability","id":"CVE-2025-48977","kev_date_added":null,"published":"2026-05-28"},{"cvss_score":7.5,"headline":"Apache Ignite communicates to an external PHP server where sensitive information is sent","id":"CVE-2017-7686","kev_date_added":null,"published":"2017-06-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Apache Software Foundation"]},"summary":"Attackers can execute arbitrary code by sending malicious serialized objects to Apache Ignite endpoints due to missing class whitelisting.","url":"https://insights.sbomify.com/CVE-2018-1295/"}