- Sep 22, 2014
- 1,767
Source: Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Multiple Security Issues - 2016-03-17T03:00:00 PDT | Symantec
Overview
Symantec Endpoint Protection (SEP) was susceptible to a number of security findings that could potentially result in an authorized but less privileged user gaining elevated access to the Management Console. SEP Client security mitigations can potentially be bypassed allowing arbitrary code execution on a targeted client.
Details
The management console for SEPM contained a cross-site request forgery vulnerability that was the result of an insufficient security check in SEPM. An authorized but less-privileged user could potentially include arbitrary code in authorized logging scripts. When submitted to SEPM, successful execution could possibly result in the user gaining unauthorized elevated access to the SEPM management console with application privileges.
There was a SQL injection found in SEPM that could have allowed an authorized but less-privileged SEPM operator to potentially elevate access to administrative level on the application.
The sysplant driver is loaded as part of the Application and Device Control (ADC) component on a SEP client if ADC is installed and enabled on the client. A previous security update to this driver did not sufficiently validate or protect against external input. Successfully bypassing security controls could potentially result in targeted arbitrary code execution on a client system with logged-on user privileges. Exploitation attempts of this type generally use known methods of trust exploitation requiring enticing a currently authenticated user to access a malicious link or open a malicious document in a context such as a website or in an email.
NOTE: Customers not using ADC are not impacted by the client issue, CVE-2015-8154. See Mitigations below for information on disabling the ADC driver or uninstalling ADC.
Symantec Response
Symantec product engineers have addressed these issues in SEP 12.1-RU6-MP4. Customers should update to RU6-MP4 as soon as possible 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-RU6-MP4 is available from Symantec File Connect.
Mitigations
As a workaround against the client issue, CVE-2015-8154, SEP administrators can disable the ADC driver or uninstall ADC in SEP 12.1 by following one of these options
Option 1 for SEP 12.1: Disable the Application and Device Control driver
Note: Deploying an Application and Device Control (ADC) policy is not sufficient to re-enable the driver after it has been disabled. Repairing the installation, or upgrading to a later version, will re-enable the sysplant driver automatically.
As part of normal best practices, Symantec strongly recommends the following:
Credit
Symantec would like to thank Anatoly Katyushinwith Kaspersky Labs https://www.kaspersky.com, for finding and reporting CVE-2015-8152, CVE-2015-8153 and working closely with Symantec as they were addressed.
Symantec would like to thank enSilo Research Team, https://www.ensilo.com, for reporting CVE-2015-8154 and working closely with Symantec as it was addressed.
References
CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org/cve), which standardizes identifiers for security problems.
BID: Symantec SecurityFocus, http://www.securityfocus.com, has assigned Bugtraq IDs (BIDs) to these issues for inclusion in the Security Focus vulnerability database.
Overview
Symantec Endpoint Protection (SEP) was susceptible to a number of security findings that could potentially result in an authorized but less privileged user gaining elevated access to the Management Console. SEP Client security mitigations can potentially be bypassed allowing arbitrary code execution on a targeted client.
Details
The management console for SEPM contained a cross-site request forgery vulnerability that was the result of an insufficient security check in SEPM. An authorized but less-privileged user could potentially include arbitrary code in authorized logging scripts. When submitted to SEPM, successful execution could possibly result in the user gaining unauthorized elevated access to the SEPM management console with application privileges.
There was a SQL injection found in SEPM that could have allowed an authorized but less-privileged SEPM operator to potentially elevate access to administrative level on the application.
The sysplant driver is loaded as part of the Application and Device Control (ADC) component on a SEP client if ADC is installed and enabled on the client. A previous security update to this driver did not sufficiently validate or protect against external input. Successfully bypassing security controls could potentially result in targeted arbitrary code execution on a client system with logged-on user privileges. Exploitation attempts of this type generally use known methods of trust exploitation requiring enticing a currently authenticated user to access a malicious link or open a malicious document in a context such as a website or in an email.
NOTE: Customers not using ADC are not impacted by the client issue, CVE-2015-8154. See Mitigations below for information on disabling the ADC driver or uninstalling ADC.
Symantec Response
Symantec product engineers have addressed these issues in SEP 12.1-RU6-MP4. Customers should update to RU6-MP4 as soon as possible 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-RU6-MP4 is available from Symantec File Connect.
Mitigations
As a workaround against the client issue, CVE-2015-8154, SEP administrators can disable the ADC driver or uninstall ADC in SEP 12.1 by following one of these options
Option 1 for SEP 12.1: Disable the Application and Device Control driver
Note: Deploying an Application and Device Control (ADC) policy is not sufficient to re-enable the driver after it has been disabled. Repairing the installation, or upgrading to a later version, will re-enable the sysplant driver automatically.
- From the Symantec Endpoint Protection Management (SEPM) console, withdraw the Application and Device Control policy (if applicable).
- Disable or configure Tamper Protection to allow the process for any tools or scripts used.
How to disable Tamper Protection in Symantec Endpoint Protection 12.1 - At the local client, open a Windows command shell with administrative privileges.
- Enter the following command:
sc config sysplant start= disabled
- Restart the client computer.
- From the SEPM console, enable Tamper Protection.
- From the SEPM console, click Admin > Install Packages, click Client Install Feature Set, and select Add Client Install Feature Set.
- Choose to remove Application and Device Control, and click OK.
- Navigate to Client Groups and select Add Install Packages.
- Uncheck Maintain Feature Set, and select the newly created feature set, once for 32-bit and once for 64-bit.
All SEP clients are moved to that new feature set without the ADC component installed.
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 Anatoly Katyushinwith Kaspersky Labs https://www.kaspersky.com, for finding and reporting CVE-2015-8152, CVE-2015-8153 and working closely with Symantec as they were addressed.
Symantec would like to thank enSilo Research Team, https://www.ensilo.com, for reporting CVE-2015-8154 and working closely with Symantec as it was addressed.
References
CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org/cve), which standardizes identifiers for security problems.
BID: Symantec SecurityFocus, http://www.securityfocus.com, has assigned Bugtraq IDs (BIDs) to these issues for inclusion in the Security Focus vulnerability database.
Last edited by a moderator:
