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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection File Overwrite

SYM10-013

December 15, 2010

Severity

Medium
Remote Access Yes, if Symantec Endpoint Protection Client is installed and authenticated with target server
Local Access Yes
Authentication Required Yes, request must come from authenticated Symantec Endpoint Protection Client
Exploit publicly available Proof of Concept

Overview

Symantec Endpoint Protection(SEP) Manager reporting module allows a php file overwrite from an authorized client that could potentially allow execution of arbitrary code on the server-side.

Product(s) Affected

Product Version Solution
Symantec Endpoint Protection 11.x Upgrade to SEP 11 RU6 MP2
Note: Symantec AntiVirus is not affected by this issue. The fix for this issue is in SEPM.

Details

Symantec was notified by Zero Day Initiative(ZDI) that a vulnerability in the Symantec Endpoint Protection Reporting Module had been reported to them.

Upon installation of a Symantec Endpoint Protection Client, a special encrypted, package of information called a sylink is distributed to a users machine in order for a machine be paired to a particular SEP Manager. This pairing allows for the user to receive necessary updates.

The SEP product contains a module that allows for report generation. This vulnerability allows a basic user the ability to overwrite a PHP file on reporting module, execute said file and conduct an arbitrary code execution. The attack must originate from a machine that has both the SEP Client installed and be authenticated to a SEP Manager. The attack will only work on the same SEP Manager to which the client is authenticated to.

Symantec Response

Symantec product engineers have developed and released a solution. Symantec customers should update to the latest release available through normal update procedures.

Symantec knows of no exploitation of or adverse customer impact from this issue.

Best Practices

As part of normal best practices, Symantec strongly recommends:

  • 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.
  • As a best practice Symantec recommends running the same version of SEP Client and SEPM.

Credit

Symantec thanks Andrea Micalizzi, aka rGod, working through TippingPoint’s Zero Day Initiative http://www.zerodayinitiative.com/ for bringing the issue to Symantec’s attention and ZDI for their close coordination with us through resolution.

References

Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) 45372 to this issue for inclusion in the Security Focus vulnerability database.

This issue is a candidate for inclusion in the Common Vulnerabilities and Exposures (CVE) list (http://cve.mitre.org). The CVE initiative has assigned CVE-2010-0114 to this issue.

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: December 15, 2010
Security Response Blog
The State of Spam