{"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-2020-1963 in the wild and no public exploit code.","fix":"Upgrade org.apache.ignite:ignite-core to 2.8.1 or later.","what":"CVE-2020-1963 is a critical path traversal vulnerability in Apache Ignite, published on 3 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-1963 and fix it if it is affected.\n\nWhat it is: CVE-2020-1963 is a critical path traversal vulnerability in Apache Ignite, published on 3 Jun 2020. 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-2020-1963 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.8.1\n- org.apache.ignite:ignite-core (Maven): affected all versions; fixed in 2.8.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-2020-1963/ (Markdown: https://insights.sbomify.com/CVE-2020-1963/index.md)","id":"CVE-2020-1963","markdown":"https://insights.sbomify.com/CVE-2020-1963/index.md","name":"CVE-2020-1963","record":{"aliases":["GHSA-5wm5-8q42-rhxg"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Ignite","requires_auth":"none","summary":"Attackers can exploit H2 SQL functions in Apache Ignite to access the underlying filesystem, leading to unauthorized data access or modification.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ignite","vendor":"apache"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Apache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem.","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":"File system access via H2 in Apache Ignite","id":"CVE-2020-1963","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":2,"n_references":10,"next":{"headline":"Deserialization of Untrusted Data in Apache Heron","id":"CVE-2020-1964"},"packages":[{"ecosystem":"Maven","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":null,"source":"GHSA-5wm5-8q42-rhxg"},{"ecosystem":"Maven","fixed":["2.8.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":"pkg:maven/org.apache.ignite/ignite-core","source":"GHSA-5wm5-8q42-rhxg"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-1962"},"products":["Apache Ignite"],"published":"2020-06-03","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":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-04","vendors":["n/a"]},"summary":"Attackers can exploit H2 SQL functions in Apache Ignite to access the underlying filesystem, leading to unauthorized data access or modification.","url":"https://insights.sbomify.com/CVE-2020-1963/"}