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

Security Advisories Relating to Symantec Products - Symantec Web Gateway Blind SQL Injection


January 12, 2011

Revision History




CVSS2 Base Score: 5.82

Impact 6.44, Exploitability 6.45

CVSS2 Vector: AV:A/AC:L/Au:N/C:P/I:P/A:P

Exploit Publicly Available: No


Symantec’s Web Gateway management GUI is susceptible to a blind SQL injection attack which could result in injection of arbitrary code into the backend database.

Product(s) Affected

Product Version Solution
Symantec Web Gateway 4.5 Apply DB update


Symantec was notified of a blind SQL injection vulnerability in the GUI management console of the Symantec Web Gateway Appliance. The interface fails to properly filter/validate external input.
In a normal installation, the affected management interface should not be accessible external to the network. However, an authorized but unprivileged network user or an external attacker who can leverage network access could attempt an attack against the management interface. The success exploitation of this vulnerability could potentially result in arbitrary code injection into and possible compromise of the appliance backend database.

Symantec Response

Symantec engineers have verified this issue and released an update to address it. Symantec engineers did additional reviews of related functionality to further enhance the overall security of Symantec Web Gateway. This issue is resolved in data base update which is currently available to customers. Symantec recommends all customers ensure the latest available updates are installed to protect against threats of this nature.

Customers should ensure the update is on their system as follows:

  • Log in to the Symantec Web Gateway user interface
  • Navigate to Administration->updates
  • Ensure that the Current Version is listed as (or later)
  • If the Current Version is less than, update to the latest available version

Symantec is not aware of any exploitation of, or adverse customer impact from this issue.

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.


RadLSneak reported this to Symantec via TippingPoint’s ZeroDay Initiative. Symantec would like to thank TippingPoint ZDI for reporting these issues and providing co-ordination while Symantec resolved it.


BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) 45742 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. The CVE initiative has assigned CVE-2010-0115.


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: January 12, 2011
Security Response Blog
The State of Spam