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

Security Advisories Relating to Symantec Products - Symantec Web Gateway Management Console XSS


March 13, 2017

Overview | Issues | Affected Products | Mitigation | Best Practices | Acknowledgements | Revisions




Symantec has released updates to address cross-site scripting (XSS) issues in Symantec Web Gateway (SWG) Management Console releases prior to 5.2.7


Highest severity issue: Medium
Number of issues: 1


< Back to top




This update applies to the following issues:




Symantec Web Gateway Management Console Multiple XSS prior to SWG 5.2.7




< Back to top




Symantec has verified the issues and addressed them in a product update as outlined below.



The following Symantec enterprise products are affected.



Symantec Web Gateway prior to 5.2.7

Upgrade to SWG 5.2.7


< Back to top





Symantec Web Gateway Multiple XSS in Management Console


BID: 96297

Severity: Medium (CVSSv3: 4.6) AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Impact: Script Injection

Exploitation: None

Date patched: March 13, 2017

Symantec Web Gateway fails to properly validate/sanitize certain external input, allowing the potential for reflected cross-site scripting attempts. These attempts may come from authorized, but non-privileged network users or, in some instances, from unauthorized external individuals who are able to entice an actively logged-in web console user to click on a maliciously-crafted HTML link. Successful targeting of these issues could result in an authorized Symantec Web Gateway user’s management console session with associated privileges being hijacked.

Cross-site scripting is a trust exploitation that requires enticing a previously authenticated user to click on a malicious HTML link. An external attacker would need to successfully entice an authorized, privileged Symantec Web Gateway management console user to visit a malicious web site or click on a malicious HTML link in an email in any attempt to take advantage of this issue. In a normal installation, the Symantec Web Gateway management console should not be accessible external to the network environment.



< Back to top




Symantec engineers validated these issues. A Symantec Web Gateway update, version 5.2.7, has been released to address them. Symantec Web Gateway's latest release is currently available to customers through normal support locations.

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

Customers should ensure they are on the latest release of Symantec Web Gateway, currently 5.2.7, and running the latest database 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.

Symantec will be releasing the following IPS signature to detect/prevent attempts against CVE-2016-9096 in Symantec Web Gateway. Detections will be available through normal Symantec security update channels.

26812 - Web Attack: Symantec Web Gateway XSS


< Back to top




Symantec recommends the following measures to reduce risk of attack:

  • Restrict access to administrative or management systems to authorized privileged users.
  • Restrict remote access to trusted/authorized systems only.
  • Run under the principle of least privilege, where possible, to limit the impact of potential exploit.
  • Keep all operating systems and applications current with vendor patches.
  • Follow a multi-layered approach to security. At a minimum, run both firewall and anti-malware applications 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 the detection of attacks or malicious activity related to the exploitation of latent vulnerabilities.


< Back to top




  • Sanehdeep Singh, saneh447 at gmail.com (CVE-2016-9096)



< Back to top







< Back to top



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: March 13, 2017
Security Response Blog
The State of Spam