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

Security Advisories Relating to Symantec Products - Symantec Messaging Gateway Multiple Vulnerabilities

SYM17-004

June 21, 2017

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

 

 

OVERVIEW

Symantec has released an update to address three issues that were discovered in the Symantec Messaging Gateway (SMG).

 

Highest severity issue: High
Number of issues: 3

 

< Back to top

 

 

ISSUES

This update applies to the following issues:

TITLE

CVE

SEVERITY

Symantec Messaging Gateway Remote Code Execution prior to 10.6.3 w/ patch 10.6.3-266

CVE-2017-6326

High

Symantec Messaging Gateway Disarm Bypass prior to 10.6.3 w/ patch 10.6.3-266

CVE-2017-6324

High

Symantec Messaging Gateway Local File Inclusion prior to 10.6.3 w/ patch 10.6.3-266

CVE-2017-6325

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 Messaging Gateway prior to 10.6.3

Upgrade to SMG version 10.6.3 and apply patch 10.6.3-266.

 

< Back to top

 

 

ISSUE DETAILS

 

Symantec Messaging Gateway Remote Code Execution

CVE-2017-6326

BID: 98893

Severity: High (CVSSv3: 7.6) AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Impact: Code execution

Exploitation: None

Date patched: June 19, 2017
 

The Symantec Messaging Gateway can encounter an issue of remote code execution, which describes a situation whereby an individual may obtain the ability to execute commands remotely on a target machine or in a target process.

 

 

 

Symantec Messaging Gateway Disarm Bypass

CVE-2017-6324

BID: 98889

Severity: High (CVSSv3: 7.3) AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Impact: Privilege escalation

Exploitation: None

Date patched: June 19, 2017
 

The Symantec Messaging Gateway, when processing a specific email attachment, can allow a malformed or corrupted Word file with a potentially malicious macro through despite the administrator having the ‘disarm’ functionality enabled. This constitutes a ‘bypass’ of the disarm functionality resident to the application.

 

 

Symantec Messaging Gateway Local File Inclusion

CVE-2017-6325

BID: 98890

Severity: Medium (CVSSv3: 6.4) AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Impact: Code execution

Exploitation: None

Date patched: June 19, 2017
 

The Symantec Messaging Gateway can encounter a file inclusion vulnerability, which is a type of vulnerability that is most commonly found to affect web applications that rely on a scripting run time. This issue is caused when an application builds a path to executable code using an attacker-controlled variable in a way that allows the attacker to control which file is executed at run time.

This file inclusion vulnerability subverts how an application loads code for execution. Successful exploitation of a file inclusion vulnerability will result in remote code execution on the web server that runs the affected web application.

 

< Back to top

 

 

MITIGATION

These issues were validated by the product team engineers. A Symantec Messaging Gateway update, version 10.6.3 with patch 10.6.3-266, has been released which addresses the aforementioned vulnerabilities. Please ensure you upgrade to the new version and apply the necessary patch. Note that the Symantec Messaging Gateway’s latest release is available to customers through normal support channels. For details on the patching process for Symantec Messaging Gateway, you can reference the following knowledge base article: http://www.symantec.com/docs/TECH246802

At this time, Symantec is not aware of any exploitations or adverse customer impact from these issues.

 

< 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

  • Adam Witt: accidentalassist@gmail.com (CVE-2017-6324), Mehmet Dursun Ince: mehmet@mehmetince.net (CVE-2017-6325, CVE-2017-6326)

 

< Back to top

 

 

REVISIONS

  • Added link to KB on patch process

 

 

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