CVE-2019-17635 is a vulnerability in Eclipse Memory Analyzer
Published on January 17, 2020
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.
Weakness Type
What is a Marshaling, Unmarshaling Vulnerability?
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
CVE-2019-17635 has been classified to as a Marshaling, Unmarshaling vulnerability or weakness.
Products Associated with CVE-2019-17635
Want to know whenever a new CVE is published for Eclipse Memory Analyzer? stack.watch will email you.
Affected Versions
The Eclipse Foundation Eclipse Memory Analyzer Version All versions prior to version 1.9.2 is affected by CVE-2019-17635Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.