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

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


May 17, 2012

Revision History





Base Score



CVSS2 Vector

Command injection code execution - High






File include/command execution - High






File download/deletion- Medium





Cross-site scripting - Medium







Symantec’s Web Gateway management GUI is susceptible to file include command injection/execution, file upload/execution and file download/deletion security issues.  The management GUI is also susceptible to cross-site scripting (XSS).  Successful exploitation could result in execution of arbitrary code in the context of the application, denial of service through deletion of arbitrary system files, and unauthorized access to users' data or to unauthorized network information.


Product(s) Affected




Symantec Web Gateway


Symantec Web Gateway 5.0.3




Symantec was notified of multiple security issues impacting the management console of the Symantec Web Gateway Appliance. The management interface does not properly authenticate or filter external input.  This could allow unauthorized access to user’s session or network information.  As a result of weak authentication and sanitization of user controlled input, arbitrary code could potentially be injected/included in application scripts used by the Symantec Web Gateway application potentially resulting in arbitrary command execution with application privileges. 

Additionally, file management scripts in the Symantec Web Gateway interface do not properly filter user input, potentially resulting in an unauthenticated, unprivileged user downloading and deleting arbitrary files including essential operational files. This could render the targeted system unavailable or unusable depending on the success of such an attempt and files targeted.  An unauthenticated, unprivileged user could also upload arbitrary code through the abuse of management scripts.  A malicious user could be able to control the file name and location which could potentially result in arbitrary command execution with elevated privileges.

Cross-site scripting vulnerabilities were also reported in the Symantec Web Gateway Management Interface. Cross-site scripting is a trust exploitation generally requiring enticing a authenticated user to click on a malicious link. A successful exploitation, depending on the nature of the link, could potentially result in arbitrary java/html requests and scripts executed in the context of the targeted user.

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



Symantec Response

Symantec engineers verified these issues and have released an update to address them. Symantec engineers reviewed related functionality to further enhance the overall security of Symantec Web Gateway. Symantec has released Symantec Web Gateway 5.0.3, currently available to customers through normal update channels.


Symantec is not aware of any exploitation of, or adverse customer impact from these issues.

Best Practices

As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.
  • Disable remote access or restrict it to trusted/authorized systems 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


Symantec credits Tenable Network Security working through TippingPoint’s ZeroDay Initiative  for reporting file include, command injection/execution and file download/deletion and upload/execution issues.


Symantec credits an anonymous contributor working with Beyond Security's SecuriTeam Secure Disclosure project (http://www.beyondsecurity.com/ssd.html for reporting file include, command injection/execution; file download/deletion and upload/execution issues.


Symantec credits Ajay Pal Singh Atwal and an anonymous finder for reporting the cross-site scripting issues.



BID: Security Focus, http://www.securityfocus.com, has assigned the following Bugtraq IDs (BID) to these issues for inclusion in the Security Focus vulnerability database.

BID 53444 to the file include/command execution issues

BID 53442 to the file download/deletion issues

BID 53443 to the file upload/OS command execution issue

BID 53396 to the XSS issues

CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. The following CVE IDs have been assigned.

CVE-2012-0297 to the file include/command execution issues

CVE-2012-0298 to the file download/deletion issues

CVE-2012-0299 to the file upload/OS command execution issues

CVE-2012-0296 to the XSS issues



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: May 17, 2012
Security Response Blog
The State of Spam