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

Security Advisories Relating to Symantec Products - Symantec Web Gateway Security Issues


June 16, 2014








Base Score



CVSS2 Vector

 Command Injection in SNMPConfig.php - High





SQL Injection in user.php  - Medium





Blind SQLi in clientreport.php - Medium





Reflected XSS in multiple report parameters -Medium






Symantec Web Gateway (SWG) 5.2 Appliance management console is susceptible to security issues.  Successful exploitation could result in unauthorized command execution on or access to the management console.  There is also potential for unauthorized backend database manipulation. 


Product(s) Affected




Symantec Web Gateway Appliance

5.2 and prior

Symantec Web Gateway 5.2.1

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


Symantec was notified of security issues impacting the SWG management console that could result in unauthorized access to management console functionality and the backend database. The results of successful exploitation could potentially range from unauthorized disclosure of sensitive data to possibly unauthorized privileged access to the Symantec Web Gateway Appliance.

Unauthenticated arbitrary commands can potentially be injected into application scripts accessible though the SWG consoles interface.  Successful command injection could result in arbitrary command execution with elevated privileges on the web console. 

SQL injection issues were identified allowing an authenticated SWG administrator to make unauthorized database queries.  Successful targeting could potentially result in arbitrary SQL queries to the backend database resulting in unauthorized disclosure of privileged information and/or possibly unauthorized manipulation of the database.

Some report pages on SWG versions 5.1.x and prior do not properly validate/sanitize external input allowing a blind SQL injection with the potential to run an unauthorized arbitrary SQL query vice an authorized query.  The 5.1.x version is also impacted by reflected cross-site scripting.   Successful targeting of these XSS issues could result in hijacking the SWG user session. Both of these were fully addressed in the release of SWG 5.2 so any customers still on a 5.1.x release should migrate to the latest release available which is 5.2.1.


In a normal installation, the Symantec Web Gateway management interface should not be externally accessible from the network environment.  However, an authorized but unprivileged network user or an external attacker able to successfully leverage network access could attempt to exploit these weaknesses.


Symantec Response

Symantec engineers confirmed that some of these issues were addressed in the 5.2 release of Symantec Web Gateway and have released an update to 5.2 to address additional findings. Symantec engineers continue to review related functionality to further enhance the overall security of Symantec Web Gateway. Symantec has released Symantec Web Gateway 5.2.1, currently available to customers through normal support locations.


Customers should ensure they are on the latest release of Symantec Web Gateway 5.2.1 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 “Check for Updates” 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 Brandon Perry working through HP Zero Day Initiative (ZDI) for submitting the command injection and SQL injection for SWG 5.2.  Symantec further thanks ZDI for working with us as we address them.


 Symantec thanks Min1214 of INFOSEC Inc. (http://www.skinfosec.com/en/) working through the Korean CERT, KR-CERT, and CERT.org for reporting the blind SQL injection and the XSS in 5.1.x



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 67752

Cmd Injection in SNMPConfig.php


BID 67753

SQLi in user.php


BID 67754

Blind SQLi in clientreport.php


BID 67755

Reflected XSS in multiple report parameters


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