{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17635 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17635 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17635 is a high-severity unsafe deserialization vulnerability in The Eclipse Foundation Eclipse Memory Analyzer, published on 17 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-17635 and fix it if it is affected.\n\nWhat it is: CVE-2019-17635 is a high-severity unsafe deserialization vulnerability in The Eclipse Foundation Eclipse Memory Analyzer, published on 17 Jan 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-17635 in the wild and no public exploit code.\n\nAffected product: The Eclipse Foundation Eclipse Memory Analyzer. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2019-17635/ (Markdown: https://insights.sbomify.com/CVE-2019-17635/index.md)","id":"CVE-2019-17635","markdown":"https://insights.sbomify.com/CVE-2019-17635/index.md","name":"CVE-2019-17635","record":{"aliases":["GHSA-pwc3-f5rp-xjcq"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Eclipse Memory Analyzer","requires_auth":"none","summary":"Eclipse Memory Analyzer allows local code execution if a user reopens a heap dump with a malicious index file or if local configuration data is tampered with.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"memory_analyzer","vendor":"eclipse"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Eclipse Memory Analyzer version 1.9.1 and earlier is subject to a deserialization vulnerability if an index file of a parsed heap dump is replaced by a malicious version and the heap dump is reopened in Memory Analyzer. The user must chose to reopen an already parsed heap dump with an untrusted index for the problem to occur. The problem can be averted if the index files from an untrusted source are deleted and the heap dump is opened and reparsed. Also some local configuration data is subject to a deserialization vulnerability if the local data were to be replaced with a malicious version. This can be averted if the local configuration data stored on the file system cannot be changed by an attacker. The vulnerability could possibly allow code execution on the local system.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Deserialization in Eclipse Memory Analyzer","id":"CVE-2019-17635","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Insufficient Verification of Data Authenticity in Eclipse Theia","id":"CVE-2019-17636"},"packages":[],"prev":{"headline":"Cross-site scripting in Eclipse Memory Analyzer","id":"CVE-2019-17634"},"products":["Eclipse Memory Analyzer"],"published":"2020-01-17","related":[{"cvss_score":9,"headline":"Cross-site scripting in Eclipse Memory Analyzer","id":"CVE-2019-17634","kev_date_added":null,"published":"2020-01-17"},{"cvss_score":2.8,"headline":"XML external entity in Eclipse Memory Analyzer (tools.mat)","id":"CVE-2023-6194","kev_date_added":null,"published":"2023-12-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["The Eclipse Foundation"]},"summary":"Eclipse Memory Analyzer allows local code execution if a user reopens a heap dump with a malicious index file or if local configuration data is tampered with.","url":"https://insights.sbomify.com/CVE-2019-17635/"}