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.
Metrics
Affected Vendors & Products
References
Link | Providers |
---|---|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=558633 |
History
No history.
MITRE
Status: PUBLISHED
Assigner: eclipse
Published: 2020-01-17T18:35:13
Updated: 2024-08-05T01:47:13.610Z
Reserved: 2019-10-16T00:00:00
Link: CVE-2019-17635
Vulnrichment
No data.
NVD
Status : Modified
Published: 2020-01-17T19:15:12.010
Modified: 2024-11-21T04:32:40.477
Link: CVE-2019-17635
Redhat
No data.