Cisco Cisco Firepower Management Center 2000

20

FireSIGHT System Release Notes

Resolved Issues

Verify that the appliances in your deployment are successfully communicating and that there are no issues reported 
by the health monitor.

Reapply device configurations to all managed devices.

To reactivate a grayed-out Apply button, edit any interface in the device configuration, then click Save without 

making changes.

Reapply access control policies to all managed devices.

Applying an access control policy may cause a short pause in traffic flow and processing, and may also cause a few 
packets to pass uninspected. For more information, see the FireSIGHT System User Guide.

If a patch for Version 5.4.0.3 is available on the Support site, apply the latest patch as described in the FireSIGHT 
System Release Notes for that version. 

You must update to the latest patch to take advantage of the latest enhancements and security fixes.

Resolved Issues

You can track defects resolved in this release using the Cisco Bug Search Tool (

https://tools.cisco.com/bugsearch/

). A 

Cisco account is required. To view defects addressed in older versions, refer to the legacy caveat tracking system.



 Addressed multiple vulnerabilities in SSLv3 that allowed external attacks on client connections, as 

described in CVE-2015-0286,CVE-2015-0287, CVE-2015-0289, CVE-2015-0292, and CVE-2015-0293.



Addressed a cross-site scripting (XSS) vulnerability, as described in CVE-2015-0707.



Addressed multiple vulnerability issues in Linux and other third parties, as described in 

CVE-2011-2699, CVE-2012-2744, CVE-2012-3400, and CVE-2015-1781.



Addressed a vulnerability in HTTP connection handling that allowed users to be redirected to 

malicious websites, as described in CVE-2015-0706.



Resolved an issue where the system can experience a microengine fault based on malformed packet 

data in traffic inspected by a FirePOWER 7000 or 8000 Series managed device. (CSCuu10871, CSCuu26678)



When routing is configured on a Series 3 device, the system may forward source-routing IPv4 packets, which direct 
the packet along a different path than configured on the router and can be used to bypass network security 
measures. (132121/CSCze88520)



Resolved an issue where, if you viewed the threat score of some files from generated events, the system incorrectly 
reported the threat score as a number instead of Low, Medium, High, or Very High. (142290/CSCze93722)



Improved URL filtering. (144198/CSCze94590)



Resolved an issue where the passive interfaces on 7000 Series devices reported incorrect egress security zones 
and interfaces. (144624/CSCze95206)



Resolved an issue where, if you edited the interface security zones from the Object Management page, the stacked 
device configuration appeared to be up-to-date when it wasn't. (144626/CSCze94847)



Resolved an issue where, if you enabled remote storage and created a scheduled email alert response on your 
Defense Center, the scheduled email alert disabled remote storage and remote storage backups failed. 
(145288/CSCze95993)



Resolved an issue where access control rules containing web application conditions did not match against traffic if 
users on your network entered a URL into the address bar that was not lowercase. (CSCur37364)