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

Security Advisories Relating to Symantec Products - Symantec Management Console XSS/XXE Issues

SYM17-005

June 28, 2017

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

 

 

OVERVIEW

Symantec has released an update to address two issues that were discovered in the Symantec Management Console (SMC).

 

Highest severity issue: Medium
Number of issues: 2

 

< Back to top

 

 

ISSUES

This update applies to the following issues:

TITLE

CVE

SEVERITY

Symantec Management Console Multiple XSS prior to ITMS 8.1 RU1, ITMS 8.0_POST_HF6 & ITMS 7.6_POST_HF7

CVE-2017-6322

Medium

Symantec Management Console Multiple XXE prior to ITMS 8.1 RU1 ITMS 8.0_POST_HF6 & ITMS 7.6_POST_HF7

CVE-2017-6323

Medium

 

< Back to top

 

 

AFFECTED PRODUCTS

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

 

Enterprise

The following Symantec enterprise products are affected.

PRODUCT

SOLUTION

Symantec Management Console prior to ITMS 8.1 RU1, ITMS 8.0_POST_HF6 & ITMS 7.6_POST_HF7

Upgrade to SMC version ITMS 8.1 RU1 or apply patches ITMS 8.0_POST_HF6 & ITMS 7.6_POST_HF7 to previous releases.

 

< Back to top

 

 

ISSUE DETAILS

 

Symantec Management Console Multiple XSS

CVE-2017-6322

BID: 98653

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

Impact: Cross site scripting

Exploitation: None

Date patched: June 19, 2017
 

Symantec Management Console fails to properly validate/sanitize certain external input, allowing the potential for reflected cross-site scripting attempts. These attempts may come from authorized, but non-privileged network users or, in some instances, from unauthorized external individuals who are able to entice an actively logged-in management console user to click on a maliciously-crafted HTML link. Successful targeting of these issues could result in an authorized Symantec Management Console user’s management session with associated privileges being hijacked.

 

Cross-site scripting is a trust exploitation that requires enticing a previously authenticated user to click on a malicious HTML link. An external attacker would need to successfully entice an authorized, privileged Symantec Management Console user to visit a malicious web site or click on a malicious HTML link in an email in any attempt to take advantage of this issue. In a normal installation, the Symantec Management console should not be accessible external to the network environment.

 

Symantec Management Console Multiple XXE

CVE-2017-6323

BID: 98621

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

Impact: Information disclosure

Exploitation: None

Date patched: June 19, 2017
 

The Symantec Management Console has an issue whereby XML input containing a reference to an external entity is processed by a weakly configured XML parser. This attack may lead to the disclosure of confidential data, denial of service, server side request forgery, port scanning from the perspective of the machine where the parser is located, and other system impacts.

 

XML external entity (XXE) attacks may allow disclosure of local files, which may contain sensitive data such as passwords or private user data. The attack uses file URI schemes or relative paths in the system identifier to access files that should not normally be accessible. Since the attack occurs relative to the application processing the XML document, an attacker may use this trusted application to pivot to other internal systems, possibly disclosing other internal content via HTTP(S) requests or launching a CSRF attack to any unprotected internal services.

 

 

< Back to top

 

 

MITIGATION

This issue was validated by the product team engineers. A Symantec Management Console set of updates, version ITMS 8.1 RU1 as well as patches ITMS 8.0_POST_HF6 & ITMS 7.6_POST_HF7, have been released which address the aforementioned vulnerabilities. Note that the Symantec Management Console’s latest release and patches are available to customers through normal support channels. At this time, Symantec is not aware of any exploitations or adverse customer impact from these issues.

 

< 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

  • Korprit Zombie: korprit@gmail.com (CVE-2017-6322, CVE-2017-6323)

 

 

< Back to top

 

 

REVISIONS

  • None

 

 

< 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: June 28, 2017
Security Response Blog
The State of Spam