{"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-2017-7686 in the wild and no public exploit code.","fix":"Upgrade org.apache.ignite:ignite-core to 2.1 or later.","what":"CVE-2017-7686 is a high-severity vulnerability in Apache Ignite, published on 28 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-7686 and fix it if it is affected.\n\nWhat it is: CVE-2017-7686 is a high-severity vulnerability in Apache Ignite, published on 28 Jun 2017. 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-2017-7686 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.1\n- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 2.1\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-2017-7686/ (Markdown: https://insights.sbomify.com/CVE-2017-7686/index.md)","id":"CVE-2017-7686","markdown":"https://insights.sbomify.com/CVE-2017-7686/index.md","name":"CVE-2017-7686","record":{"aliases":["GHSA-8p83-68cw-943f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Ignite","requires_auth":"none","summary":"Apache Ignite's update notifier sends sensitive system properties to an external server, potentially exposing user information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ignite","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","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 communicates to an external PHP server where sensitive information is sent","id":"CVE-2017-7686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Denial of service in Apache Mesos","id":"CVE-2017-7687"},"packages":[{"ecosystem":"Maven","fixed":["2.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":null,"source":"GHSA-8p83-68cw-943f"},{"ecosystem":"Maven","fixed":["2.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":"pkg:maven/org.apache.ignite/ignite-core","source":"GHSA-8p83-68cw-943f"}],"prev":{"headline":"Apache OpenMeetings responds to insecure HTTP methods","id":"CVE-2017-7685"},"products":["Apache Ignite"],"published":"2017-06-28","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.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"}],"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-08-05","vendors":["Apache Software Foundation"]},"summary":"Apache Ignite's update notifier sends sensitive system properties to an external server, potentially exposing user information.","url":"https://insights.sbomify.com/CVE-2017-7686/"}