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

Security Advisories Relating to Symantec Products - Symantec Client IDS Driver PE File Memory Corruption Denial of Service


July 7, 2016


8/23/2016 - Added Def build info to SEP Solutions for clarification

Severity CVSS v3


Base Score

CVSS3 Vector

Symantec CIDS Driver PE file Memory Corruption DOS - Medium




Symantec's Client Intrusion Detection System (CIDS) driver may cause a system crash when interacting with a specifically-crafted Portable Executable file.

Affected Products





Norton Security

Windows Only


Update to CIDS v15.1.2 via LiveUpdate Defs

Symantec Endpoint Protection

Windows Only


Update to CIDS v15.0.6 via LiveUpdate Defs 7/7/2016 rev. 14 (20160707.014)


Symantec was notified of a system crash, Denial of Service (DoS) in the CIDS engine driver when interacting with a specifically-crafted portable-executable (PE) files. A malicious individual would first need to entice an authorized user to download a malformed PE file either through opening an email attachment, downloading a malicious document or application or by enticing the user to visit a web site where a malicious file could be downloaded to their system. Once downloaded, the malicious file must be manipulated on the targeted system hard drive to interact with the vulnerable CIDS engine.

Sufficiently malformed, the code would execute at the kernel-level with system privileges causing memory corruption resulting in a system crash.

Symantec Response

Symantec engineers have addressed this in the latest CIDS engine update release effective 7/7/2016 delivered to customers via LiveUpdate with normal definition and signature updates.

Update Information

Norton Security and SEP products that ship with the CIDS engine and regularly launch and run either automatic or manual LiveUpdate should already have received an updated CIDS engine version addressing this issue. However, to ensure all available updates have been applied, users should manually launch and run LiveUpdate in Interactive mode as follows:

To perform a manual update using Symantec LiveUpdate, users should:

  • Access LiveUpdate in the product

  • Run LiveUpdate until all available updates are downloaded and installed

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

Best Practices

As part of normal best practices, Symantec strongly recommends the following:

  • Restrict access to administrative or management systems to authorized 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 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.


Discovered by Piotr Bania of Cisco Talos. Symantec would like to thank Cisco Talos 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 (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.






Symantec CIDS Driver PE file Memory Corruption DOS


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