1. Symantec/
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Symantec Endpoint Encryption Client Memory Dump Information Disclosure


December 14, 2015




CVSS2 Base Score



CVSS2 Vector

Symantec Endpoint Encryption Client Memory Dump Information Disclosure - Medium






Symantec’s Endpoint Encryption (SEE) Client is susceptible to information disclosure if a user with access to a system hosting a client is able to force a client memory dump and access the content of the memory dump. This could result in unauthorized exposure of such things as stored credentials used by the client in communicating with components of the SEE management server (SEEMS).

Product(s) Affected





Symantec Endpoint Encryption

11.0 and prior


Symantec Endpoint Encryption 11.1.0


Symantec was notified of an information disclosure isse in SEE clients. An authorized but unprivileged client user with SEE installed on their system who can force and access a memory dump of the SEE Framework Service, EACommunicatorSrv.exe, may have unauthorized access to credentials stored on the client such as the Domain user credentials protecting the SEEMS web service. This could potentially allow an unprivileged user to attempt unauthorized access to additional systems hosting other clients through web services. This access is dependent on the privileges afforded to the Domain user credentials.

Symantec Response

Symantec product engineers fully addressed these issues in SEE 11.1.0. Recommend customer upgrade to the latest release of SEE to prevent any potential impact from this issue.

NOTE: SEEMS installation/security configuration documentation has always recommended Domain user credentials NOT have logon privileges.

Symantec is not aware of exploitation of or adverse customer impact from this issue.

Update information

Symantec Endpoint Encryption 11.1.0 is available through Symantec File Connect.

Best Practices

As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.

  • Disable remote access if not required or restrict it to trusted/authorized systems only.

  • Where possible, limit exposure of application and web interfaces to trusted/internal networks only.

  • Keep all operating systems and applications updated with the latest vendor patches.

  • Follow a multi-layered approach to security. Run both firewall and anti-malware applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.

  • Deploy network and host-based intrusion detection systems to monitor network traffic for signs of anomalous or suspicious activity. This may aid in detection of attacks or malicious activity related to exploitation of latent vulnerabilities

Symantec thanks Julio Auto, Principal Information Security Engineer at Mayo Clinic, for reporting this and working with us as we addressed it.


BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) to this issue for inclusion in the Security Focus vulnerability database.

CVE: This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.





BID 78803

Symantec Endpoint Encryption Client Memory Dump Information Disclosure

Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows responsible disclosure guidelines.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be found at the location below.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Copyright (c) by Symantec Corp.

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Product Security, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: December 14, 2015
Security Response Blog
The State of Spam