Cisco Cisco Firepower Management Center 4000 Release Notes

Version 5.3.0.6

Sourcefire 3D System Release Notes

27

Resolved Issues

Resolved an issue where, in some cases, the system restore boot option 

did not output to the serial port on managed devices even if you selected 

Physical Serial Port as the remote console access option. (130772)

Improved the stability of clustered managed devices when failing over after 

a hardware failure. (130811, 130812, 131031, 133088, 130602)

Resolved a failover synchronization issue on clustered managed devices. 

(130829)

Improved the system's malware analysis and blocking capabilities when 

handling file transfer protocol (FTP) traffic. (130888, 133134)

Resolved an issue where, in rare cases, the intrusion policy page failed to 

display. (131181)

Resolved an issue where, in rare cases, the table view of servers (Analysis > 

Hosts > Servers) duplicated servers and produced inaccurate server counts. 

(131329)

Resolved an issue where, in some cases, if you configured static routes as 

described in KB article 000001950 and made a subsequent change to the 

network configuration, the system dropped the static routes until after the 

next system reboot. (131646)

Improved the stability of stacking three managed devices in a Tri-Stack. 

(131836, 131896)

Resolved an issue where the system misplaced the home directory files for 

user accounts after updating to a major version of the Sourcefire 3D 

System. (132503)

Resolved an issue where disabling the Quoted-Printable Decoding Depth 

advanced option in your intrusion policy did not prevent the system from 

generating events on intrusion rule 124:11. (132538)

Resolved an issue where, if you configured a custom table populated with 

data from the Correlation Events table and the Applications table, then 

selected Source IP as a common field, updates to Version 5.3 failed. 

(135735)

Resolved an issue where, in some cases, if you configured an access 

control policy with a Monitor rule (which forces end-of-connection logging) 

and a Trust rule with Log at Beginning of Connection enabled, the system did 

not generate end-of-connection events for matching SSH-encrypted traffic. 

(135952)