Cisco Cisco Email Security Appliance C690 Notas de publicación
What’s New in Cisco IronPort AsyncOS 7.5.1 for Email
2
Release Notes for Cisco IronPort AsyncOS 7.5.1 for Email
OL-25139-02
What’s New in Cisco IronPort AsyncOS 7.5.1 for
Email
This section describes the resolved issues in Cisco IronPort AsyncOS 7.5.1 for
Email.
Email.
Fixed Issues in Release 7.5.1
The following issues have been fixed in this release of AsyncOS for Email.
Table 1
Resolved Issues in Version 7.5.1
Defect ID
Description
83262
Fixed: FreeBSD telnetd Remote Code Execution Vulnerability
This hot patch fixes a vulnerability in the Cisco IronPort Email Security appliance that
could have allowed a remote, unauthenticated attacker to execute arbitrary code with
elevated privileges.
could have allowed a remote, unauthenticated attacker to execute arbitrary code with
elevated privileges.
For more information on the vulnerability, see the Cisco security advisory at
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-2012
0126-ironport
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-2012
0126-ironport
82012
Fixed: Appliance may stop accepting new email messages
After reboot, an appliance upgraded to AsyncOS 7.5.1-026 may suspend all listeners,
causing the appliance to stop accepting incoming email messages. If you suspect this
issue, enter the
causing the appliance to stop accepting incoming email messages. If you suspect this
issue, enter the
status detail
command in the CLI. If this issue has occurred, the
Resource Conservation line will show 999.
78178
Fixed: Appliance May Become Unresponsive
Previously, a C660, C670, X1060, or X1070 appliance would become unresponsive
after processing a high amount of message traffic with large attachments over an
extended period of time. This issue required the work queue, scanning engines, and
other AsyncOS features to be handling a constant high level of traffic in order to
create the excessive memory usage that caused the appliance to become unresponsive.
This issue has been resolved.
after processing a high amount of message traffic with large attachments over an
extended period of time. This issue required the work queue, scanning engines, and
other AsyncOS features to be handling a constant high level of traffic in order to
create the excessive memory usage that caused the appliance to become unresponsive.
This issue has been resolved.