Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mat-dev] Two security issues fixed in Memory Analyzer
  • From: "Tsvetkov, Krum" <krum.tsvetkov@xxxxxxx>
  • Date: Fri, 17 Jan 2020 21:03:54 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sap.com; dmarc=pass action=none header.from=sap.com; dkim=pass header.d=sap.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VgwqOeiiexiEXHnR8sJdTrheXSprgJ3njCk9kG2ixiA=; b=EGDWiYFDutUQMoXvVAn54Eb/zt59bqrTaBmKDP0nJyeXuHcWSlnABb9YE9a+y/dxiNT2418oLmB2gY8DeUAV4aOyn5unjX9XK3N5fBi9ZD/qvoVXxksFhNEb/fQ617G1KNJvyz6o2eWHCrTfNE6ZYKEt46SsbIX+Y8GUCtNTbS3l9FwpGvIXAcDTLKVflWPPiE6PywZPDLk4V/6DTPSaZgg1cArV6bzfIDJey8sIdpDIqzjBc7+1qcyfIhHFboWVLRagvVEuzXputCFqZr8CPRh8SmPYtjurG6eExxKzA0xvljjqOCFw6nMCRDcl7IrJx268thM6vBEWwILhP4OzVg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mNJATyjio8Wt1hqnqF5Pa/RH3MvypJFsXQ0YJxYm3hDH6EiSfGLtAldJCPYLEhSu8HqI8FwO6GRqNRNnnnIPU4Ib7n4UGIt6/SVi4CKm85dgjgR0qf+tyUkOIH56SOJnoozZ1dybTPHHMK9+zbiVmuTdKqQeD2/aFFXVa3zLIkJujeCHhUIb01iaxBRAZFXx4FgLy96tdr+k7YTnnsz2Lu6do2cVXUq0iheRpWK3O6jdDDyCgdc0tt4yDg4JZiFhtOBJ+zUstyE5BkYTjYrTtcitMBj/X6Sp88VwvSdEg5XLe7MQiv44v2bu2P5EvXglGz4P00P/VWdjwQGTNrMD9Q==
  • Delivered-to: mat-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/mat-dev>
  • List-help: <mailto:mat-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/mat-dev>, <mailto:mat-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/mat-dev>, <mailto:mat-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHVzXmgqcppmNliNEeKYVRNcZxQfA==
  • Thread-topic: Two security issues fixed in Memory Analyzer
  • User-agent: Microsoft-MacOutlook/10.21.0.200113

Hi all,

 

Two security issues have been identified in Memory Analyzer.

The issues have the following CVEs assigned CVE-2019-17634 and CVE-2019-17635. Details about both issues are below.

 

We have released Memory Analyzer 1.9.2 with fixes for both issues.

We highly recommend updating to the version 1.9.2 – on the downloads page there are as usual references to standalone packages as well as an update-site.

 

CVE-2019-17634  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17634

[PROBLEMTYPE]:CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

 [DESCRIPTION]: Eclipse Memory Analyzer version 1.9.1 and earlier is subject to a cross site scripting (XSS) vulnerability when generating an HTML report from a malicious heap dump. The user must chose todownload, open the malicious heap dump and generate an HTML report for the problem to occur. The heap dump could be specially crafted, or could come from a crafted application or from an application processing malicious data. The vulnerability is present whena report is generated and opened from the Memory Analyzer graphical user interface, or when a report generated in batch mode is then opened in Memory Analyzer or by a web browser. The vulnerability could possibly allow code execution on the local system whenthe report is opened in Memory Analyzer.

 

Thanks to Iassen Minov for reporting the issue.

 

CVE-2019-17635  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17635

[PROBLEMTYPE]:CWE-502: Deserialization of Untrusted Data

[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.

 

Regards,

Krum Tsvetkov

Back to the top