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.
Symantec has developed a Software Security Vulnerability Management Process document outlining the process we follow in addressing suspected vulnerabilities in our products.
Symantec Corporation firmly believes in a proactive approach to secure software development and implements security review into various stages of the software development process. Additionally, Symantec is committed to the security of its products and services as well as to its customers’ data. Symantec is committed to continually improving its software security process.
This document provides an overview of the current Secure Development Lifecycle (SDLC) practice applicable to Symantec’s product and service teams as well as other software security related activities and policies used by such teams. This document is intended as a summary and does not represent a comprehensive list of security testing and practices conducted by Symantec in the software development process.
Please contact secure@symantec.com if you believe you have discovered a security issue in a Symantec product. A member of the Symantec Software 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 Software Security PGP key can be found at the following location:
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.
Last modified on: December 14, 2015
Security Response Blog
The State of Spam