Security Advisories Relating to Symantec Products - Symantec Web Gateway Blind SQL Injection
July 7, 2011
CVSS2 Base Score: 5.82
Impact 6.4, 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 blind SQL injection which could result in the injection of arbitrary code into the backend database.
Symantec Web Gateway
Upgrade to Symantec Web Gateway 5.0.1
Symantec was notified of a blind SQL injection vulnerability in the 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 is able to leverage network access could attempt such an attack against the management interface. The successful exploitation of this vulnerability could potentially result in arbitrary SQL command input to the backend database.
Symantec engineers have verified this issue and released an update to address it. This issue is resolved in Symantec Web Gateway 5.0.1 currently available to customers through normal update channels.
Symantec is not aware of any exploitation of, or adverse customer impact from this issue.
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
BID:Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) 48318 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-2011-0549.
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 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 email@example.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 firstname.lastname@example.org.
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 email@example.com.