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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Clients Local Elevation of Privilege, CSV Formula Injection

SYM17-002

March 6, 2017

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

 

 

OVERVIEW

Symantec has released updates to address security issues reported in both Symantec Endpoint Protection 12.1 and Symantec Endpoint Protection 14.0 Windows clients.

 

Highest severity issue: Medium
Number of issues: 2

 

< Back to top

 

 

ISSUES

This update applies to the following issues:

TITLE

CVE

SEVERITY

Symantec Endpoint Protection Windows Client 12.1 SymEvent Driver Local Elevation of Privilege

CVE-2016-9093

Medium

Symantec Endpoint Protection Windows Client CSV Formula Injection In Exported Quarantine Files

CVE-2016-9094

Low 

 

< Back to top

 

 

AFFECTED PRODUCTS

Symantec has verified the reported issues and addressed them in product updates as indicated below.

 

Enterprise

The following Symantec enterprise products are affected.

PRODUCT

SOLUTION

Symantec Endpoint Protection 14.0 (Windows) impacted by

CVE-2016-9094

Update to SEP 14.0 MP1

Symantec Endpoint Protection 12.1 RU6 MP6 (Windows) and earlier impacted by

CVE-2016-9093, CVE-2016-9094

Update to SEP 12.1 RU6 MP7

 

< Back to top

 

 

ISSUE DETAILS

Symantec Endpoint Protection Windows Client 12.1 SymEvent Driver Local Elevation of Privilege

CVE-2016-9093

BID: 96294

Severity: Medium (CVSSv3: 6.7) AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Impact: Privilege escalation

Exploitation: None


 

A version of the SymEvent Driver that shipped with Symantec Endpoint Protection 12.1 RU6 MP6 and earlier fails to properly sanitize logged-in user input. SEP 14.0 and later are not impacted by this issue.

A non-admin user would need to be able to save an executable file to disk and then be able to successfully run that file. If properly constructed, the file could access the driver interface and potentially manipulate certain system calls. On all 32-bit systems and in most cases on 64-bit systems, this will result in a denial of service that will crash the system. In very narrow circumstances, and on 64-bit systems only, this could allow the user to run arbitrary code on the local machine with kernel-level privileges. This could result in a non-privileged user gaining privileged access on the local machine.

 

 

Symantec Endpoint Protection Windows Clients 12.1 and 14.0 CSV Formula Injection in Exported Quarantine Files

CVE-2016-9094

BID: 96298

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

Impact: Formula Injection

Exploitation: None

 

Symantec Endpoint Protection clients place detected malware in quarantine as part of the intended product functionality. The quarantine logs can be exported for review by the user in a variety of formats including .CSV files. The potential exists for file metadata to be interpreted and evaluated as a formula. Successful exploitation of an attack of this type requires considerable direct user-interaction from the user exporting and then opening the log files on the intended target client.

 

< Back to top

 

 

MITIGATION

Update Information: Symantec Endpoint Protection 12.1 RU6 MP7 and 14.0 MP1 are available through Symantec File Connect. When applied, these updates will assure that systems are not vulnerable to either issue described in this advisory. Symantec recommends that all customers apply our product updates as soon as they become available.

 

< Back to top

 

 

BEST PRACTICES

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

 

 

ACKNOWLEDGEMENTS

  • Alexandre GAZET of Air Bus Group, working through Air Bus Group CERT, for his extensive coordination with Symantec while we addressed the issue (CVE-2016-9093)
  • Raghav Bisht, raghav007bisht at gmail.com (CVE-2016-9094)

 

< Back to top

 

 

REVISIONS

  • 3/9/2017 – Revised content to clarify that windows-only versions of SEP 12.1 RU6 and SEP 14.0 are impacted by these issues.

 

< Back to top

 

REPORTING VULNERABILITIES TO SYMANTEC

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:
COPYRIGHT (C) BY SYMANTEC CORP.
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: March 6, 2017
Security Response Blog
The State of Spam