06-03-2024 10:06 PM - edited 06-16-2024 11:55 PM
I noticed a new odd behaviour of ASA 9.18.4.22. Object-group and object duplicate and dependency checks no longer work. It used to complain when one edits an object-group and adds an object that already existed. Now nothing shown at all. Also it used to complain when deleting an object that it could not be deleted because it was still in use by an object-group or an access-list.
firewall1/context2/act# show run object-group id Some-Object-Group
object-group network Some-Object-Group
network-object 1.0.0.0.0 255.0.0.0
network-object 2.0.0.0.0 255.0.0.0
network-object 3.0.0.0.0 255.0.0.0
firewall1/context2/act# conf t
firewall1/context2/act(config)# object-group network Some-Object-Group
firewall1/context2/act(config-network-object-group)# network-object 3.0.0.0.0 255.0.0.0
firewall1/context2/act(config-network-object-group)# exit
On a firewall with an older release (e.g. Version 9.16(3)23) adding a duplicate network-object shows a warning like this:
WARNING: Adding obj (network-object 3.0.0.0 255.0.0.0) to grp (Some-Object-Group) failed; object already exists
Don't know if that was before on that version, but definitely not on a version prior to 9.18.4.x. We don't have this behaviour on ASA firewalls running 9.16.x.
On ASA 9.18.4.24 deleting an network-object that was used in an object-group showed no error that the network-object is still used in an object-group. Instead ASA adds a duplicate network-object in same object-group:
firewall1/context2/act(config)# show run object-group id dummy-group-1
object-group network dummy-group-1
network-object object dummy-object-1
network-object object dummy-object-2
firewall1/context2/act(config)# show run object id dummy-object-1
object network dummy-object-1
host 1.0.0.0
firewall1/context2/act(config)# show run object id dummy-object-2
object network dummy-object-2
host 2.0.0.0
firewall1/context2(config)# no object network dummy-object-1
firewall1/context2(config)# show run object-group id dummy-group-1
object-group network dummy-group-1
network-object object dummy-object-1
network-object object dummy-object-2
network-object object dummy-object-1
Removing duplicate causes firewall to panic and reboot.
firewall1/context2/act(config)# object-group network dummy-group-1
firewall1/context2/act(config-network-object-group)# no network-object object dummy-object-1
Coredump starting....
Corehelper: /opt/cisco/csp/cores/core.lina.10.1266.1717407923
Waiting for Corehelper to finish....
Livecore: generating coredump of 1266
[New LWP 1377]
[New LWP 1378]
[New LWP 1379]
[New LWP 1380]
[New LWP 1382]
[New LWP 1383]
[New LWP 1384]
[New LWP 1385]
[New LWP 1386]
[New LWP 1387]
[New LWP 1388]
[New LWP 1389]
[New LWP 1390]
[New LWP 1391]
[New LWP 1392]
[New LWP 1393]
[New LWP 1394]
0x000000fff79a474c in pthread_cond_timedwait () from /lib64/libpthread.so.0
warning: target file /proc/1266/cmdline contained unexpected null characters
Solved! Go to Solution.
06-23-2024 09:51 PM
Cisco declared this bug as a new feature since 9.18.1 ...
Firewall Features | |||
Forward referencing of ACLs and objects is always enabled. In addition, object group search for access control is now enabled by default. | You can refer to ACLs or network objects that do not yet exist when configuring access groups or access rules. In addition, object group search is now enabled by default for access control for new deployments. Upgrading devices will continue to have this command disabled. If you want to enable it (recommended), you must do so manually.
We removed the forward-reference enable command and changed the default for new deployments for object-group-search access-control to enabled. |
https://www.cisco.com/c/en/us/td/docs/security/asa/asa918/release/notes/asarn918.html
I wonder why this behaviour was changed. Getting ready for integrating ASA into Firewall Management Center from FTD?
06-11-2024 12:06 PM
Does somebody else encounter this bug or know in which release it will be fixed? We have it on ASA 9.18.4.22.
06-11-2024 10:20 PM
It also affects objects and object-groups used by access-lists. An object or object-group used by an access-list can be removed without an error. The access-list line still exists, but points to a non-existing object or object group.
06-16-2024 11:59 PM
06-17-2024 06:25 AM
Please tell us bug id if TAC opens one.
06-17-2024 06:34 AM
I will. They probably name the bug after me. I found so many.
06-23-2024 09:51 PM
Cisco declared this bug as a new feature since 9.18.1 ...
Firewall Features | |||
Forward referencing of ACLs and objects is always enabled. In addition, object group search for access control is now enabled by default. | You can refer to ACLs or network objects that do not yet exist when configuring access groups or access rules. In addition, object group search is now enabled by default for access control for new deployments. Upgrading devices will continue to have this command disabled. If you want to enable it (recommended), you must do so manually.
We removed the forward-reference enable command and changed the default for new deployments for object-group-search access-control to enabled. |
https://www.cisco.com/c/en/us/td/docs/security/asa/asa918/release/notes/asarn918.html
I wonder why this behaviour was changed. Getting ready for integrating ASA into Firewall Management Center from FTD?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide