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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Privilege Assumption, Policy Bypass, Local Elevation of Privilege

SYM14-001

January 9, 2014

Revisions

 

None

 

Severity

 

CVSS2

Base Score

Impact

Exploitability

CVSS2 Vector

SEPM Insufficient User Validation Privilege Assumption - Medium

6.3

10.0

2.0

AV:A/AC:H/AU:M/C:C/I:C/A:C

SEP Client ADC Security Policy Bypass Unauthorized File Access - Medium

4.1

6.4

2.7

AV:L/AC:M/AU:S/C:P/I:P/A:P

SEP Client Unquoted Search Path Local Elevation of Privilege - Medium

6.6

10.0

2.7

AV:L/AC:M/AU:S/C:C/I:C/A:C

 

Overview

The Management Console in Symantec Endpoint Protection does not properly validate user authentication, which could potentially allow a user to assume another user’s identity and privileges on the console. 

Symantec Endpoint Protection clients do not sufficiently restrict custom policies, which could potentially lead to directory/file access by an unauthorized user.

Symantec Endpoint Protection clients have unquoted search paths, which could allow a non-privileged local user to potentially run arbitrary code.

Affected Products

Product

Version

Build

Solution(s)

Symantec Endpoint Protection

11.x

All

Upgrade to SEP 11.0.7.4 or the latest release of SEP 12.1.x

Symantec Endpoint Protection Small Business Edition

12.0

All

Upgrade to latest release of SEP 12.1.x

Symantec Endpoint Protection

12.1.x

All prior to 12.1.2 (RU2)

Upgrade to latest release of SEP 12.1.x

 

Details

Symantec’s Endpoint Protection Manager does not properly validate the authentication of authorized users.   This could potentially permit an authorized but limited access administrator to leverage full admin privileged access.  Any authorized user who can access a limited admin account could potentially assume the identification and privileges of any other authorized console user to include full admin.

The Application/Device Control (ADC) in Symantec Endpoint Protection clients does not sufficiently enforce some custom polices.  An authorized but non-privileged user could potentially bypass restrictions set up via ADC policies and access unauthorized directories/files on a system. 

NOTE:  This custom policy bypass does not permit a non-privileged user to bypass normal file system permissions (ACLs).  A user bypassing custom policy restrictions in this manner will not be able to access files or directories in violation of established ACLs.

Symantec Endpoint Protection clients are susceptible to an unquoted search path issue. This could potentially allow an authorized but non-privileged local user to execute arbitrary code with elevated privileges on the client system.  Successful targeting 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 where it could potentially be executed during application startup or reboot.  If successful, their code could potentially execute with client application privileges.

Symantec Response
Symantec product engineers verified these issues and resolved them in the Symantec Endpoint Protection releases identified above.

Update Information

Updates are available through customers’ normal support/download locations.

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. 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

Credit
Symantec thanks Matthew Hembree for the security policy bypass reported in Symantec Endpoint Protection Manager Application/Device Control and for working closely with us as we resolved it.

Symantec credits Jennia Hizver for reporting the user identity and privilege assumption in Symantec Endpoint Protection Manager and for working closely with us as we resolved it.

Symantec credits Anand Bhat and Timothy McKenzie for identifying unquoted search paths in Symantec Endpoint Protection.

References

BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq IDs (BIDs) to these issues for inclusion in the Security Focus vulnerability database.

CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. 

 

CVE

BID

Description

CVE-2013-5009

BID 64128

SEPM Insufficient User Validation Privilege Assumption

CVE-2013-5010

BID 64129

SEP Client ADC Security Policy Bypass Unauthorized File Access

CVE-2013-5011

BID 64130

SEP Client Unquoted Search 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.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product 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 Product Security PGP key can be found at the location below.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

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 Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com

Disclaimer

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Product Security, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: January 9, 2014
Security Response Blog
The State of Spam