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

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

SYM14-015

November 5, 2014

Revisions

 

12/9/2014 – Updated mitigations to include SPC v1

 

7/6/2015 – Updated mitigation "Disabling SPC v1 web console access" to properly reflect required steps.

 

Severity

 

CVSS2

Base Score

Impact

Exploitability

CVSS2 Vector

SEPM Unauthenticated XML External Entity Injections (XXE) - High

7.5

6.4

10

AV:N/AC:L/Au:N/C:P/I:P/A:P

SEPM Multiple Reflected Cross-Site Scripting (XSS) -Medium

4.3

2.9

8.6

AV:A/AC:M/Au:N/C:P/I:P/A:N

SEPM Arbitrary File Write/Overwrite - Medium

6.1

6.9

6.5

AV:A/AC:L/Au:N/C:N/I:N/A:C


Overview

The management console for Symantec Endpoint Protection Manager (SEPM) is susceptible to multiple vulnerabilities including XML External Entity Injection, reflected cross-site scripting and the potential for arbitrary file write/overwrite.

Affected Products

Product

Version

Build

Solution(s)

Symantec Endpoint Protection Manager

12.1

All

Update to 12.1 RU5.

 

Product Not Affected

Product

Version

Symantec Endpoint Protection (SEP) clients

All

Symantec Network Access Control (SNAC)

All

Symantec Endpoint Protection Manager

11.0.x

Symantec Protection Center Small Business Edition

12.0.x

 

Details

The management console for Symantec Endpoint Protection Manager (SEPM) does not properly validate incoming XML data, which could potentially allow unauthorized access to restricted server-side data and to potentially leverage additional console management functionality. An attempt to exploit this type of vulnerability would require any attacker to successfully impersonate or hijack the input source of external information/updates for SEPM or to be able to successfully inject their arbitrary XML code into an incoming XML stream.

SEPM is also susceptible to reflected XSS issues existing in the interface scripts used to manage the console.  The management console does not provide sufficient validation/sanitation of incoming input.  Successful targeting could allow an unauthorized individual to steal the session cookies or hijack the browser session being used to manage the console.  This could potentially allow unauthorized user-level access to the management console.

Arbitrary file write vulnerability in the ConsoleServlet could allow an attacker to write or overwrite arbitrary files in the context of the web server.  This is due to improper filtering of user-supplied data to the logging component.  This could possibly allow arbitrary code to be written to the log file and potentially to disk.  This attempt would likely result in a denial of service server disruption.  However, if successful, this could lead to unauthorized elevated access on the server.

In a recommended installation, the Symantec Endpoint Protection Manager server should not be accessible external to the network which would still allow internal attack attempts from malicious non-privileged users but should restrict external attack attempts. However, a malicious, non-authorized individual could leverage known methods of trust exploitations to compromise a client user in an attempt to gain network/system access.  These exploitation attempts generally require enticing a previously authenticated user to access a malicious link in a context such as a web link or in an HTTP email

The potential to leverage the remote access XXE vulnerabilities to facilitate further attempts against local access functionality could increase the overall severity of a successful attack against the application.  A successful attack could potentially allow application-level access to the server.

Symantec Response
Symantec product engineers verified these issues.  SEPM 12.1 RU5 contains updates that prevent these issues from occurring.
Customers should implement the mitigations described below until the available update can be installed to address these issues.  Symantec is not aware of exploitation of or adverse customer impact from this issue.

Update Information

Symantec Endpoint Protection Manager 12.1 RU5 is available from Symantec File Connect.


Mitigations

If unable to update to 12.1.5 (RU5) immediately, a SEP administrator has two options.

1.      Restrict web console access and SPC v1 to localhost

2.      Disable web console access available under https://localhost:8443/console and SPC v1 under https://localhost:8443/portal

 

Restricting web console access to localhost

1.      Open [SEPM Installation directory]\tomcat\conf\server.xml in a text editor.

2.      Find the following entry:  <Context crossContext="true" docBase="ajaxswing" path="/console" reloadable="false"/>

3.      Edit this line to look like this:
<Context crossContext="true" docBase="ajaxswing" path="/console" reloadable="false">
<Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1"/>
</Context>

4.      Restart SEPM service.

 

Restricting SPC v1 access to localhost

1.      Open [SEPM Installation directory]\tomcat\conf\server.xml in a text editor.

2.      Find the following entry:  <Context crossContext="true" docBase="/portal.war" path="/portal" reloadable="false">

3.      Edit this line to look like this:
<Context crossContext="true" docBase="/portal.war" path="/portal" reloadable="false">
<Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1"/>
</Context>

4.      Restart SEPM service.

 

Disabling web console access

To disable the web console access, follow these steps:

 

1.      Open [SEPM Installation directory]\tomcat\conf\server.xml in a text editor.

2.      Comment out the following line:
<!-- <Context crossContext="true" docBase="ajaxswing" path="/console" reloadable="false"/> -->

3.      Stop the SEPM service.

4.      If exists, delete this folder and all of its contents: [SEPM installation folder]\tomcat\webapps\ajaxswing

5.      Start the SEPM service.

6.      This action will prevent launching of the Web Console until this mitigation is removed.

Note: The SEPM console is not impacted by this and will continue to work as expected.

 

Disabling SPC v1 web console access

To disable the web console access, follow these steps:

 

1.      Open [SEPM Installation directory]\tomcat\conf\server.xml in a text editor.

2.      Comment out the following line:
<!-- <Context crossContext="true" docBase="portal.war" path="/portal" reloadable="false"/> -->

3.      Stop the SEPM service.

4.      If exists, delete this file: [SEPM installation folder]\tomcat\webapps\Portal.war

5.      If exists, delete this folder and all of its contents: [SEPM installation folder]\tomcat\webapps\portal

6.      Start the SEPM service.

7.      This action will prevent launching of the Web Console until this mitigation is removed.

 

Symantec will be releasing the following IPS signatures

27803 Web Attack: Symantec Endpoint Manager XXE 2

27804 Web Attack: Symantec Endpoint Manager XSS

to detect/prevent attempts against these issues in SEPM. These detections will be available through normal Symantec security update channels.


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.

Credit


Symantec would like to thank Stefan Viehböck with SEC Consult Vulnerability Lab for reporting these issues and working very closely with Symantec as they were addressed.


Symantec would like to thank Iñaki Rodríguez, @virtualminds_es, for reporting one of the cross-site scripting issues and working with Symantec as it was addressed.

 

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-2014-3437

BID 70843

Unauthenticated XML External Entity Injection

CVE-2014-3438

BID 70844

Multiple Reflected Cross-Site Scripting

CVE-2014-3439

BID 70845

Arbitrary File Write/Overwrite

 

 

 

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