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

Security Advisories Relating to Symantec Products - Symantec Web Gateway Security Management Console Multiple Security Issues


February 10, 2014








Base Score



CVSS2 Vector

Unauthenticated XSS in .php scripts - High





Authenticated Access XSS - Medium





Authenticated Access SQL Injections –Medium







Symantec Web Gateway (SWG) Appliance management console is susceptible to both local and remote access cross-site scripting (XSS) and local access SQL injection (sqli) vulnerabilities.  Successful exploitation may result in an authorized user gaining unauthorized access to files on the management console or possibility being able to manipulate the backend data base.  There is also potential for remote hijacking of an authorized user session with associated privileges.


Product(s) Affected




Symantec Web Gateway Appliance

5.1.1 and prior

Symantec Web Gateway 5.2

 NOTE:  Customers should always ensure they are running the latest data base updates available


Symantec was notified of security issues impacting the Symantec Web Gateway management console. The results of successful exploitation could potentially range from a user with authorized access to the management console gaining unauthorized access to sensitive data or another user’s account to unauthorized manipulation of the backend application database.


Local access SQL injection issues were identified allowing an authenticated Symantec Web Gateway user to make unauthorized database queries.  Successful targeting could potentially result in unauthorized disclosure of privileged information and/or possible unauthorized manipulation of the backend database.


Symantec Web Gateway in certain cases does not properly validate/sanitize external input allowing the potential of cross-site scripting attempts by both authorized but non-privileged and in some instances unauthorized individuals.   Successful targeting of these issues could result in unauthorized access by an authorized but unprivileged user or potentially allowing an unauthorized individual to hijack an authorized Symantec Web Gateway user session with associated privileges.

Symantec Response

Symantec engineers validated these submissions, having also identified these types of issues during internal testing.  An updated Symantec Web Gateway version, 5.2, has been released to address them. Symantec Web Gateway 5.2 is currently available to customers through normal support locations.  Symantec is not aware of exploitation of or adverse customer impact from this issue.

Customers should ensure they are on the latest release of Symantec Web Gateway 5.2 and running the latest data base update. To confirm customers are running the latest updates check the “Current Software Version -> Current Version” on the Administration->Updates page.  Alternatively, customers can click the “Check for Updates” button on the Administration->Updates page to verify that they are running the latest software version.

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.
  • The Symantec Web Gateway software and any applications that are installed on the Symantec Web Gateway can ONLY be updated with authorized and tested versions distributed by Symantec.
  • 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



Symantec thanks Shaun Bertrand, Creative Breakthroughs Inc, for reporting the local access XSS and SQLi issues; Comrade Polar Bear for reporting an unauthenticated XSS issue; and William Costa, william.costa@gmail.com, for reporting an unauthenticated XSS issue.  Symantec thanks all of them for working with us as we resolved their findings.




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. 







BID 65404

SQL Injection


BID 65405

Cross-Site Scripting





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