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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Multiple Issues


November 6, 2017

Overview | Issues | Affected Products | Mitigation | Best Practices | Acknowledgements | Revisions




Symantec has released a set of updates to address three issues in the Symantec Endpoint Protection (SEP) product.


Highest severity issue: High
Number of issues: 3


< Back to top




This update applies to the following issues:




SEP Privilege Escalation



SEP Arbitrary File Deletion



SEP Tamper-Protection Bypass




< Back to top




Symantec has verified the issues and addressed them in product updates for SEP outlined below.



The following Symantec enterprise products are affected.



Symantec Endpoint Protection prior to SEP 12.1 RU6 MP9 for CVE-2017-13681

Upgrade to Symantec Endpoint Protection SEP 12.1 RU6 MP9

Symantec Endpoint Protection prior to SEP 12.1 RU6 MP9 & SEP 14 RU1 for CVE-2017-13680

Upgrade to Symantec Endpoint Protection SEP 12.1 RU6 MP9 or SEP 14 RU1

Symantec Endpoint Protection 12.1.X & prior to SEP 14 RU1 for CVE-2017-6331

Upgrade to Symantec Endpoint Protection SEP 14 RU1


< Back to top





Symantec Endpoint Protection Privilege Escalation


BID: 101504

Severity: High (CVSSv3: 8.8) (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)

Impact: Privilege escalation

Exploitation: None

Date patched: October 20, 2017

The Symantec Endpoint Protection Windows endpoint could be susceptible to a privilege escalation vulnerability, which is a type of issue that allows a user to gain elevated access to resources that are normally protected at lower access levels. In the circumstances of this issue, the capability of exploit is limited by the need to perform multiple file and directory writes to the local filesystem and as such, is not feasible in a standard drive-by type attack.


Symantec Endpoint Protection Arbitrary File Deletion


BID: 101503

Severity: Medium (CVSSv3: 6.5) (AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H)

Impact: Arbitrary File Deletion

Exploitation: None

Date patched: October 20, 2017

The Symantec Endpoint Protection Windows endpoint can encounter a situation whereby an attacker could use the product’s UI to perform unauthorized file deletes on the resident file system.


Symantec Endpoint Protection Tamper-Protection Bypass


BID: 101502

Severity: Low (CVSSv3: 2.8) (AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N)

Impact: Tamper-Protection Bypass

Exploitation: None

Date patched: October 20, 2017

The Symantec Endpoint Protection Windows endpoint can encounter an issue of Tamper-Protection Bypass, which is a type of attack that bypasses the real time protection for the application that is run on servers and clients. Tamper Protection protects Symantec processes and internal objects from these attacks that non-Symantec processes such as worms, Trojan horses, viruses, and security risks could make. Note that in this circumstance, the tamper-protection bypass only allows altering a small amount of text in one element of the UI.



< Back to top




This issues listed above were validated by the product team engineers. A set of Symantec Endpoint Protection updates, versions SEP 12.1 RU6 MP9 and SEP 14 RU1, have been released which address the aforementioned issues. Please ensure you apply the necessary patches and upgrades accordingly. Symantec Endpoint Protection's latest releases are available to customers through normal support channels. At this time, Symantec is not aware of any exploitations or adverse customer impact from these issues.

Note1: For customers running SEP 14, SEP 14 MP1 or SEP 14 MP2, only the low and medium severity issues articulated in the aforementioned advisory details affect the updated SEP 14 product line. The high severity issue does not impact any instances of SEP 14.

Note2: The aforementioned vulnerabilities only pertain to the SEP client. The SEPM manager is not affected.


< Back to top




Symantec recommends the following measures to reduce risk of attack:

  • Restrict access to administrative or management systems to authorized privileged users.
  • Restrict remote access to trusted/authorized systems only.
  • Run under the principle of least privilege, where possible, to limit the impact of potential exploit.
  • Keep all operating systems and applications current with vendor patches.
  • Follow a multi-layered approach to security. At a minimum, run both firewall and anti-malware applications 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 the detection of attacks or malicious activity related to the exploitation of latent vulnerabilities.


< Back to top




  • Matthieu Buffet on behalf of ANSSI (CVE-2017-13681)
  • Clément Lavoillotte @clavoillotte (CVE-2017-13680)
  • John Page AKA hyp3rlinx Apparitionsec (CVE-2017-6331)



< Back to top




-          Minor edit on Nov 6th, 2017

-          Added details on specific SEP endpoints

-          Minor edit to adjust finder contact details


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