Deserialization in Eclipse Memory Analyzer

CVE-2019-17635

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.

Vulnerability class: Insecure Deserialization

EPSS: 0.013 (68.4th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Affected products

Weakness classification (CWE)

References

  • emo@eclipse.org (x_refsource_CONFIRM, Exploit, Patch, Issue Tracking, Vendor Advisory)

Frequently asked questions

What is CVE-2019-17635?
CVE-2019-17635 is a high-severity vulnerability in Eclipse Memory Analyzer, classified under Deserialization of Untrusted Data. CVSS score: 7.8/10. Published 2020-01-17.
How severe is CVE-2019-17635?
High severity. CVSS v3 base score is 7.8 out of 10.