Cisco Cisco Firepower Management Center 2000 Notas de publicación
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
19
FireSIGHT System Release Notes
Version 5.3.1.1
Resolved Issues
•
Resolved an issue where, if you registered an ASA FirePOWERdevice to a pair of Defense Centers
in a high availability configuration, the secondary Defense Center did not display the CSM Single
Sign-On tab on the User Management page (
in a high availability configuration, the secondary Defense Center did not display the CSM Single
Sign-On tab on the User Management page (
System > Local > User Management
). (141150)
•
Resolved an issue where syslog alerts contained incorrect intrusion rule classification data when
sent as intrusion event notifications. (141213, 141216, 141220)
sent as intrusion event notifications. (141213, 141216, 141220)
•
Resolved an issue where adaptive profiles failed to take effect if you used a network variable such
as
as
$HOME_NET
as the value for Networks settings. (141225)
•
Resolved an issue where, if you created a configuration-only backup, the backup file included
extraneous discovery event data. (141246)
extraneous discovery event data. (141246)
•
Resolved an issue where, if you created a saved search that used a VLAN tag object, the system
saved the search with the value
saved the search with the value
0
in the field where you used the VLAN tag object instead. (141330)
•
Resolved an issue where, if you created a custom workflow with a large number of pages, the time
window obscured the link the to the final pages of the workflow. (141336)
window obscured the link the to the final pages of the workflow. (141336)
•
Resolved an issue where, in rare cases, the system did not generate a health alert when reapplying
device configuration failed. (141625, 141628)
device configuration failed. (141625, 141628)
•
Resolved an issue where, one or more unresponsive detection resources on a managed device after
installing an update of the vulnerability database (VDB) caused system issues. (141758)
installing an update of the vulnerability database (VDB) caused system issues. (141758)
•
Resolved an issue where, in rare cases, the system triggered an alert on the first data packet of a TCP
session from a server in which the egress interface would not be recorded. (141817)
session from a server in which the egress interface would not be recorded. (141817)
•
Resolved an issue where, in rare cases, applying multiple access control policies caused system
issues and high unmanaged disk usage health alerts. (141830)
issues and high unmanaged disk usage health alerts. (141830)
•
Resolved a third-party vulnerability in OpenSSL to address CVE-2-014-0224. (141901)
•
Improved the stability of the SMB and DCE/RPC preprocessor. (142199)
•
Resolved an issue where, if you edited an access control policy and policy apply failed, the policy
changes from the attempted policy apply were not restored to the previously applied policy.
(142907)
changes from the attempted policy apply were not restored to the previously applied policy.
(142907)
•
Resolved a third-party vulnerability in Java to address the following CVEs: CVE-2014-0429,
CVE-2013-5907, CVE-2013-5782, CVE-2013-5830, CVE-2013-1537, CVE-2013-0437,
CVE-2013-1478, CVE-2013-1480, CVE-2012-5083, CVE-2012-1531, CVE-2012-1713,
CVE-2014-0385, CVE-2013-5802, CVE-2013-2461, CVE-2013-2467, CVE-2013-2407,
CVE-2014-0460, CVE-2014-0423, CVE-2013-5905, CVE-2013-5906, CVE-2014-4264,
CVE-2013-6954, CVE-2013-6629, CVE-2013-5825, CVE-2013-4002, CVE-2013-5823,
CVE-2013-2457, CVE-2013-0440, CVE-2013-5780, CVE-2014-4244, CVE-2014-4263,
CVE-2014-0453, CVE-2014-0411, CVE-2013-0443, CVE-2013-2451, CVE-2013-5803,
CVE-2013-2415, CVE-2013-1489, CVE-2012-5085. (143620)
CVE-2013-5907, CVE-2013-5782, CVE-2013-5830, CVE-2013-1537, CVE-2013-0437,
CVE-2013-1478, CVE-2013-1480, CVE-2012-5083, CVE-2012-1531, CVE-2012-1713,
CVE-2014-0385, CVE-2013-5802, CVE-2013-2461, CVE-2013-2467, CVE-2013-2407,
CVE-2014-0460, CVE-2014-0423, CVE-2013-5905, CVE-2013-5906, CVE-2014-4264,
CVE-2013-6954, CVE-2013-6629, CVE-2013-5825, CVE-2013-4002, CVE-2013-5823,
CVE-2013-2457, CVE-2013-0440, CVE-2013-5780, CVE-2014-4244, CVE-2014-4263,
CVE-2014-0453, CVE-2014-0411, CVE-2013-0443, CVE-2013-2451, CVE-2013-5803,
CVE-2013-2415, CVE-2013-1489, CVE-2012-5085. (143620)
•
Resolved an issue where, if the system generated file events from the file traffic, the system
incorrectly truncated file event filenames with colons on several pages of the web interface.
(143666)
incorrectly truncated file event filenames with colons on several pages of the web interface.
(143666)
•
Resolved an issue where, if the system generated intrusion events matching a rule with a generator
ID (GID) other than 1 or 3, syslog alerts contained incorrect messages. (143725)
ID (GID) other than 1 or 3, syslog alerts contained incorrect messages. (143725)
•
Resolved an issue where, if you disabled any access control rules containing either an intrusion
policy or a variable set different from any enabled rules and the access control policy’s default
action, access control policy apply failed and the system experienced issues. (143870)
policy or a variable set different from any enabled rules and the access control policy’s default
action, access control policy apply failed and the system experienced issues. (143870)