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

Security Advisories Relating to Symantec Products - Symantec Messaging Gateway Management Console Reflected XSS

SYM14-006

April 22, 2014

Revisions

 

None

 

Severity

 

CVSS2

Base Score

Impact

Exploitability

CVSS2 Vector

Messaging Gateway Management Interface Reflective XSS - Medium

5.8

4.9

8.6

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


 Overview

Symantec’s Messaging Gateway management console is susceptible to a reflected cross-site scripting (XSS) issue found in one of the administrative interface pages.   Successful exploitation could result in potential session hijacking or unauthorized actions directed against the console with the privileges of the targeted user’s browser.

 

Product(s) Affected

Product

Version

Solution

Symantec Messaging Gateway

10.x - 10.5.1

Symantec Messaging Gateway 10.5.2

 

Details

Symantec was notified of a reflected XSS issue impacting Symantec’s Messaging Gateway 10.x management console. 

 

A reflected XSS issue exists in one of the interface pages used to manage the gateway as a result of insufficient validation/sanitation of user input.  Successful targeting of this weakness could allow an unauthorized individual to steal the browser cookies or hijack the browser session being used to manage the console.  This could potentially allow the unauthorized individual authorized user-level access to the management console.  The management console normally allows access to only specified users/administrators with varying levels of access depending on their requirements. 

 

In a typical installation the Symantec Messaging Gateway management interface should not be accessible external to the network environment and access should be restricted to specified users/administrators.  Web browsers used by authorized users to manage Symantec Messaging Gateway should never be used for casual browsing of external web sites during an administrative session.  These restrictions would greatly reduce exposure to external attempts against this type of issue.

 

A malicious but authorized non-privileged network user or an external attacker would need to successfully entice an authorized management console user to visit a malicious web site or click on a malicious HTML link in an email in any attempts to take advantage of this issue. 

 

 

Symantec Response

Symantec engineers verified this issue in Symantec Messaging Gateway 10.x. Symantec strongly recommends Symantec Messaging Gateway customers update to the latest release of Symantec Messaging Gateway, 10.5.2.  Symantec knows of no exploitation of or adverse customer impact from this issue.

Symantec Messaging Gateway 10.5.2 is currently available through customer’s normal update channels.

 


Best Practices

As part of normal best practices, Symantec strongly recommends:

·         Restrict access to administration or management systems to privileged users.

·         Disable remote access if not required or restrict it to trusted/authorized systems only.

·         Where possible, limit exposure of application and web interfaces to trusted/internal networks only.

·         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

Credit

Symantec credits William Costa, william.costa@gmail.com, for reporting this issue to us and coordinating with us as we resolved it. 

 

References

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

CVE: This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. 

 

 

CVE

BID

Description

CVE-2014-1648

BID 66966

Messaging Gateway Management Interface Reflective XSS

 

 

 

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