Cisco Cisco Email Security Appliance C190 Notas de publicación
2
Release Notes for Hot Patch 1 for AsyncOS 7.6.3 for Email
Resolved Issues
Resolved Issues
Click a Defect ID in the table for more information about the defect.
Known Issues
Click a Defect ID in the table for more information about the defect.
Additional Information
For additional information about AsyncOS for Email, see the Release Notes for your release at
.
Service and Support
For service and support information for Cisco Content Security appliances, see:
•
•
If you purchased support through a reseller or another supplier, please contact that supplier directly with
your product support issues.
your product support issues.
For noncritical questions and issues, you can also submit a customer support request from the appliance.
For instructions, see the User Guide or Online help.
For instructions, see the User Guide or Online help.
Defect ID
Description
A vulnerability that could allow an authenticated remote attacker to execute arbitrary code with the privileges
of the root user. For more information, see
of the root user. For more information, see
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20140319-asyncos
.
You will lose the network configuration of your Email Security appliance if you are reverting back after an
AsyncOS for Email upgrade. The symptom is observed when you upgrade AsyncOS for Email from version
7.5.2-203 to 7.6.3-019, and revert back to version 7.5.2-203.
AsyncOS for Email upgrade. The symptom is observed when you upgrade AsyncOS for Email from version
7.5.2-203 to 7.6.3-019, and revert back to version 7.5.2-203.
Defect ID
Description
When you upgrade to the latest version of AsyncOS for Email with expired Sophos Engine, an alert is sent
to the user stating that the Sophos Engine has expired.
to the user stating that the Sophos Engine has expired.
Workaround: You can ignore this alert. After the upgrade, auto-update will download and update the
Sophos Engine.
Sophos Engine.
Application fault occurs while adding a Recipient Address entry with more than 53 email addresses to
Recipient Access Table (RAT) using GUI.
Recipient Access Table (RAT) using GUI.
Workaround: From the application fault screen, navigate back to the Add to Recipient Access Table page
using the browser Back button, and perform the commit.
using the browser Back button, and perform the commit.