CVE-2019-17635: High severity eclipse memory analyzer vulnerability
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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2019-17635?
CVE-2019-17635 has been assigned a medium severity level due to its deserialization vulnerability.
How do I fix CVE-2019-17635?
To fix CVE-2019-17635, upgrade Eclipse Memory Analyzer to a version later than 1.9.1.
What versions are affected by CVE-2019-17635?
Eclipse Memory Analyzer versions 1.9.1 and earlier are affected by CVE-2019-17635.
What type of vulnerability is CVE-2019-17635?
CVE-2019-17635 is a deserialization vulnerability.
How can I mitigate the risk of CVE-2019-17635?
To mitigate the risk of CVE-2019-17635, avoid opening heap dumps with untrusted index files.