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

Security Advisories Relating to Symantec Products - Symantec Web Gateway Management Console Interface Command Injection

SYM16-017

October 5, 2016

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

 

 

OVERVIEW

Symantec has released an update to address a Symantec Web Gateway (SWG) Management Console Interface command injection issue bypassing validation restrictions to add an unauthorized whitelist entry.

 

Highest severity issue: Medium
Number of issues: 1

 

< Back to top

 

 

ISSUES

This update applies to the following issues:

TITLE

CVE

SEVERITY

Symantec Web Gateway Management Console Interface Command Injection

CVE-2016-5313

Medium

 

< Back to top

 

 

AFFECTED PRODUCTS

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

 

Enterprise

The following Symantec enterprise products are affected.

PRODUCT

SOLUTION

Symantec Web Gateway

Prior to SWG 5.2.5

Update to SWG 5.2.5

 

< Back to top

 

 

ISSUE DETAIL

 

Symantec Web Gateway Management Console Interface Command Injection

CVE-2016-5313

BID: 93284

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

Impact: Security bypass

Exploitation: None

Date patched: August 2, 2016
 

 

The Symantec Web Gateway Management Console allows some specially crafted entries to update the whitelist without validation. A lower-privileged but authorized management console user can bypass the whitelist validation using a specifically-modified script to create an unauthorized whitelist entry. This whitelist entry could potentially be leveraged in further malicious attempts against the network.

 

< Back to top

 

 

MITIGATION

The Symantec Web Gateway management console interface should never be accessible external to the authorized network or by any users other than an authorized management console user

 

< Back to top

 

 

BEST PRACTICES

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

 

 

ACKNOWLEDGEMENTS

  • Egidio Romano of Karma(In)Security (CVE-2016-5313)

 

 

< Back to top

 

 

REVISIONS

None

 

< Back to top

 

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 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:
COPYRIGHT (C) BY SYMANTEC CORP.
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: October 5, 2016
Security Response Blog
The State of Spam