{"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-2016-6805 in the wild and no public exploit code.","fix":"Upgrade org.apache.ignite:ignite-core to 1.9 or later.","what":"CVE-2016-6805 is a medium-severity vulnerability in n/a, published on 7 Apr 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-2016-6805 and fix it if it is affected.\n\nWhat it is: CVE-2016-6805 is a medium-severity vulnerability in n/a, published on 7 Apr 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-2016-6805 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 1.9\n- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 1.9\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-2016-6805/ (Markdown: https://insights.sbomify.com/CVE-2016-6805/index.md)","id":"CVE-2016-6805","markdown":"https://insights.sbomify.com/CVE-2016-6805/index.md","name":"CVE-2016-6805","record":{"aliases":["GHSA-8qfc-cvjp-mgpq"],"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":"Man-in-the-middle attackers can read arbitrary files via XXE in modified update-notifier documents in Apache Ignite.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ignite","vendor":"apache"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"Apache Ignite before 1.9 allows man-in-the-middle attackers to read arbitrary files via XXE in modified update-notifier documents.","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":"Moderate severity vulnerability that affects org.apache.ignite:ignite-core","id":"CVE-2016-6805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xxe","year":"2016"},"n_packages":2,"n_references":2,"next":{"headline":"Apache Wicket vulnerable to CSRF attacks","id":"CVE-2016-6806"},"packages":[{"ecosystem":"Maven","fixed":["1.9"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":null,"source":"GHSA-8qfc-cvjp-mgpq"},{"ecosystem":"Maven","fixed":["1.9"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":"pkg:maven/org.apache.ignite/ignite-core","source":"GHSA-8qfc-cvjp-mgpq"}],"prev":{"headline":"Privilege escalation in Apache OpenOffice","id":"CVE-2016-6804"},"products":["n/a"],"published":"2017-04-07","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"},{"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-08-06","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can read arbitrary files via XXE in modified update-notifier documents in Apache Ignite.","url":"https://insights.sbomify.com/CVE-2016-6805/"}