3/2/2005 – Added CVE Candidate CAN-2005-0618
Medium (Highly configuration dependent)
Symantec responded to a potential vulnerability identified in the SMTP binding function of the entry-level Symantec Gateway Security appliances with the ISP load-balancing capabilities. In certain firmware versions, the SMTP (outbound email) traffic would be load-balanced regardless of the user-configured WAN binding selection. This could result in SMTP traffic intended only for a trusted network potentially being passed over an untrusted connection instead.
|Symantec Firewall/VPN Appliance 200/200R||firmware builds prior to build 1.68 and later than 1.5Z|
|Symantec Gateway Security 360/360R||firmware builds prior to build 858|
|Symantec Gateway Security 460/460R||firmware builds prior to build 858|
|Nexland Pro800turbo||firmware builds prior to build 1.6X and later than 1.5Z|
Symantec was notified of this potential vulnerability in a Symantec Gateway Security 360 appliance configured to load-balance two ISPs with SMTP binding set for a single WAN. The SMTP binding configuration was not being implemented as selected causing SMTP traffic to be load-balanced through both WAN1 and WAN2. This could result in a potential vulnerability if a trusted network was selected for SMTP binding through one WAN and an untrusted network connected to the other WAN. SMTP traffic bound to the trusted network could potentially be passed over both the trusted and untrusted WANs (load-balanced).
Symantec confirmed the potential vulnerability and determined that the issue was also present in the Symantec Gateway Security 460, Symantec Firewall/VPN Appliance 200, and the legacy Nexland Pro800turbo models that also provide load-balancing capabilities.
Symantec has released the following firmware releases that address this issue:
- Build 1.68: Symantec Firewall/VPN Appliance models 200 and 200R
- Build 858: Symantec Gateway Security Appliance models 360 and 360R
- Build 1.6X: Nexland Pro800turbo
Symantec recommends customers using SMTP binding in load-balanced configurations apply the appropriate firmware for their affected product models/versions to remedy this issue.
Product specific firmware and hotfixes are available via the Symantec Enterprise Support site at http://www.symantec.com/techsupp.
The Common Vulnerabilities and Exposures (CVE) initiative has assigned CVE Candidate CAN-2005-0618 to this issue.
This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.
Symantec appreciates the actions of Arthur Hagen, Broomstick Net Services, in identifying this issue, notifying Symantec and providing extensive cooperation and coordination while Symantec resolved the issue.
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 the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).
Please contact firstname.lastname@example.org if you feel you have discovered a security issue in a Symantec product. A Symantec Product Security team member will contact you regarding your submission. Symantec strongly recommends using encrypted email for reporting vulnerability information to email@example.com. The Symantec Product Security PGP key can be found at the end of this message.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.
Copyright (c) 2009 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 Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
Last modified on: Wednesday, 02-Mar-05 22:39:19