{"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-2024-52577 in the wild and no public exploit code.","fix":"Upgrade org.apache.ignite:ignite-core to 2.17.0 or later.","what":"CVE-2024-52577 is a critical unsafe deserialization vulnerability in Apache Ignite, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-52577 and fix it if it is affected.\n\nWhat it is: CVE-2024-52577 is a critical unsafe deserialization vulnerability in Apache Ignite, published on 14 Feb 2025. 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-2024-52577 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.ignite:ignite-core (Maven): affected from 2.6.0; fixed in 2.17.0\n- org.apache.ignite:ignite-core (Maven): affected from 2.6.0; fixed in 2.17.0\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-2024-52577/ (Markdown: https://insights.sbomify.com/CVE-2024-52577/index.md)","id":"CVE-2024-52577","markdown":"https://insights.sbomify.com/CVE-2024-52577/index.md","name":"CVE-2024-52577","record":{"aliases":["GHSA-8355-xj3p-hv6q"],"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":"An attacker can execute arbitrary code on Apache Ignite servers by sending crafted messages that bypass serialization filters.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ignite","vendor":"apache"}],"cvss":{"score":9.5,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"In Apache Ignite versions from 2.6.0 and before 2.17.0, configured Class Serialization Filters are ignored for some Ignite endpoints. The vulnerability could be exploited if an attacker manually crafts an Ignite message containing a vulnerable object whose class is present in the Ignite server classpath and sends it to Ignite server endpoints. Deserialization of such a message by the Ignite server may result in the execution of arbitrary code on the Apache Ignite server side.","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 Ignite: Possible RCE when deserializing incoming messages by the server node","id":"CVE-2024-52577","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"Server-Side Request Forgery vulnerability in various APIs in Misskey","id":"CVE-2024-52579"},"packages":[{"ecosystem":"Maven","fixed":["2.17.0"],"introduced":["2.6.0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":null,"source":"GHSA-8355-xj3p-hv6q"},{"ecosystem":"Maven","fixed":["2.17.0"],"introduced":["2.6.0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":"pkg:maven/org.apache.ignite/ignite-core","source":"GHSA-8355-xj3p-hv6q"}],"prev":{"headline":"Memory corruption in Teamcenter Visualization V14.2","id":"CVE-2024-52574"},"products":["Apache Ignite"],"published":"2025-02-14","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.8,"headline":"Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization","id":"CVE-2018-1295","kev_date_added":null,"published":"2018-04-02"},{"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-14","vendors":["Apache Software Foundation"]},"summary":"An attacker can execute arbitrary code on Apache Ignite servers by sending crafted messages that bypass serialization filters.","url":"https://insights.sbomify.com/CVE-2024-52577/"}