Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Eclipse | Memory Analyzer | <= 1.9.1 |
Related Weaknesses (CWE)
References
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=558633ExploitIssue TrackingPatch
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=558633ExploitIssue TrackingPatch
FAQ
What is CVE-2019-17635?
CVE-2019-17635 is a vulnerability with a CVSS score of 7.8 (HIGH). 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 ...
How severe is CVE-2019-17635?
CVE-2019-17635 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2019-17635?
Check the references section above for vendor advisories and patch information. Affected products include: Eclipse Memory Analyzer.