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

Security Advisories Relating to Symantec Products - Symantec Endpoint Encryption Unquoted Service Path Local Elevation of Privilege


May 6, 2016


5/23/2016 - Added Symantec Endpoint Encryption 8.x to the Not Affected Products table


CVSS2 Base Score

CVSS2 Vector

Symantec Endpoint Encryption unquoted service path local elevation of privilege - Medium



CVSS3 Base Score

CVSS3 Vector

Symantec Endpoint Encryption unquoted service path local elevation of privilege - Medium




Symantec Endpoint Encryption (SEE) has an unquoted search path in EEDService. This could provide a non-privileged local user the ability to successfully insert arbitrary code in the root path.

Affected Products





Symantec Endpoint Encryption



Upgrade to SEE 11.1.1

Products Not Affected



Symantec PGP Desktop

10.31 and later

Symantec Endpoint Encryption 8.x



Symantec was notified of an unquoted search path issue impacting the EEDService deployed in Symantec Endpoint Encryption. An authorized but non-privileged local user could potentially leverage this issue to execute arbitrary code with elevated privileges on the system. A successful attempt would require the local user to be able to insert their code in the system root path undetected by the OS or other security applications/settings where it could potentially be executed during application startup or reboot. If successful, the local user's code would execute with the elevated privileges of the application.

Symantec Response

Symantec engineers verified this issue and have resolved it in Symantec Endpoint Encryption 11.1.1. Symantec is not aware of exploitation of or adverse customer impact from this issue.

Update Information

Update to SEE 11.1.1 will be available through Symantec File Connect. Customers should apply this update to avoid potential incidents of this nature.

Best Practices
Symantec strongly recommends as part of normal best practices:

  • Restrict access to 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 would like to thank Darshan G Parab for reporting this to us and working with us as we addressed the issue.


BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BIDs) 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.






Symantec Endpoint Encryption unquoted service path local elevation of privilege


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: May 6, 2016
Security Response Blog
The State of Spam