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

Security Advisories Relating to Symantec Products - Symantec Encryption Management Server Web Email Protection View User’s Email


February 5, 2014








Base Score



CVSS2 Vector

Symantec Encryption Management Server Email Protection View User’s Email - Medium







Symantec Encryption Management Server was susceptible to an authorized/authenticated web console user being able to view any other user’s stored outbound emails.  The issue is in the Web Email Protection component not sufficiently restricting authorized user content access. This could allow an authenticated web console user to view the content of another user’s outbound emails.


Affected Products





Symantec Encryption Management Server / Symantec PGP Universal Server

All prior to 3.3.2



Upgrade to Symantec Encryption Management Server 3.3.2



Symantec is aware of an issue existing in the Symantec Encryption Management Server web management console.  The Web Email Protection component does not sufficiently restrict user access to the content of stored emails. An authorized network user with a valid account on the web management console can manipulate the URL for his/her own authorized outbound email allowing viewing of another user’s stored mail content.  Successful exploitation could potentially result in unauthorized access to potentially sensitive information.


Symantec Response
Symantec had previously verified this reported issue during internal testing .  Symantec Encryption Management Server 3.3.2 is not vulnerable to this issue.  Customers should upgrade to Symantec Encryption Management Server 3.3.2 to avoid incidents of this nature.  Symantec is not aware of exploitation of or adverse customer impact from this issue.


Update Information

Symantec Encryption Management Server 3.3.2 is available from Symantec File Connect.


Best Practices
As part of normal best practices, Symantec strongly recommends that customers:

  •  Restrict access of administration or management systems to privileged users.
  •  Restrict remote access, if required, to trusted/authorized systems only.
  •  Run under the principle of least privilege where possible to limit the impact of   exploit by threats.
  •  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 credits
Richard O'Donnell working through Portcullis Computer Security Ltd, for reporting this issue.


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: The issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.








Symantec Encryption Management Server Web Email Protection View Users Email


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: February 5, 2014
Security Response Blog
The State of Spam