Corsaire Limited Security Advisory 020121-001c.txt
Symantec Enterprise Firewall versions 6.5.x and 7.0
Corsaire Limited discovered an issue with the way Symantec Enterprise Firewall handled SNMP notify alerts that could cause alerts to be dropped in certain instances.
Note: The SNMP notify daemon issue addressed by Corsaire Limited in their Advisory is NOT related to CERT Advisory CA-2002-03, Multiple Vulnerabilities in Many Implementations of the Simple Network Management Protocol (SNMP).
Corsaire Limited notified Symantec Corporation of an issue in the way Symantec Enterprise Firewall handled some event alerts. This issue could, potentially, result in the failure of event alerts to be logged or the administrator to be notified.
Symantec Enterprise Firewall provides many methods to alert an administrator about firewall log events based on the functionality of a subsystem called the Notify daemon. One of these notification methods sends SNMP traps to the network management station where they are centrally managed. However, if the firewall log entry exceeds an established size threshold, the Notify daemon drops the SNMP trap and logs a "failed to notify" error message instead.
In the event that SNMP is the only alert mechanism used, the administrator may fail to receive notifications for which he or she has established alert criteria.
Symantec has verified the logging issues identified by Corsaire Limited. The problem exists in the way the Notify daemon allocates the buffer size for the SNMP traps. In certain instances, while encoding the SNMP trap, the message may exceed the allocated buffer size. In these instances, the SNMP trap is dropped and the error message is logged.
Note: This problem is a notification handling issue only. The issue does not allow unauthorized access to the system nor is it possible to maliciously create a DoS condition using this issue.
To address this SNMP issue, Symantec has developed hotfixes available for download for affected versions:
Symantec takes the security of its products very seriously. Symantec appreciates the coordination of Martin O'Neal and Corsaire Limited in identifying and providing technical details of potential areas of concern so it can quickly address 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 email@example.com 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 firstname.lastname@example.org. 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 © 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 email@example.com.
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 firstname.lastname@example.org 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: Monday, 25-Oct-2004 14:45:42 PDT