Cisco Cisco Content Security Management Appliance M380 Notas de publicación

In reporting and tracking searches, second-level domains (regional domains listed at 

) are treated differently from subdomains, even though the two 

domain types may appear to be the same. For example: 

Reports will not include results for a two-level domain such as 

co.uk

, but will include results for 

foo.co.uk

. Reports include subdomains under the main corporate domain, such as 

cisco.com

. 

Tracking search results for the regional domain 

co.uk

 will not include domains such as 

foo.co.uk

, 

while search results for 

cisco.com

 will include subdomains such as 

subdomain.cisco.com

. 

84905

Previously, application faults could occur when clicking Identities or Access policies in Configuration 
Master 7.5 after an unsuccessful publish. 

85307

Fixed: Loading a configuration file fails after reverting to AsyncOS 7.8.0-564 

If the Security Management appliance manages one or more Web Security appliances running AsyncOS 7.5, 
a workaround was required in order to load a configuration file after reverting. The workaround is no longer 
required. 

82692

Previously, in rare circumstances, SNMP could drive CPU usage to 100%. This problem has now been 
fixed.

83075

Previously, searching Web Tracking data generated an out of memory error when the tracking data contained 
large amounts of data. This no longer occurs. Now, when you click the Related Transactions link, the web 
interface displays up to 500 transaction and displays “[Omitted]” when it omits transactions. Also, 
extremely long URLs are truncated to 1000 characters, and “[truncated]” in the displayed URL. 

83262 

Previously, there was a vulnerability that could have allowed a remote, unauthenticated attacker to execute 
arbitrary code with elevated privileges.

For more information about the vulnerability, see the Cisco security advisory at