The recommended resolution is to upgrade to a remediated software version at your earliest convenience. Arista recommends customers move to the latest version of each release that contains all the fixes listed below. For more information about upgrading see EOS User Manual: Upgrades and Downgrades https://www.arista.com/en/um-eos/eos-upgrades-and-downgrades CVE-2023-3646 has been fixed in the following releases: * 4.28.6M and later releases in the 4.28.x train * 4.29.2F and later releases in the 4.29.x train

HotfixThe following hotfix can be applied to remediate CVE-2023-3646. The hotfix only applies to the releases listed below and no other releases. All other versions require upgrading to a release containing the fix (as listed above): * 4.28.2F through 4.28.5.1M releases in the 4.28.x train * 4.29.1F and earlier releases in the 4.29.X train Note: Installing/uninstalling the Hotfix will result in a restart of the SandFapNi agent and an associated reprogramming of the switch chip. This process could result in outages from 5-20 minutes, depending on the number of active ports in the particular system. To determine which hotfix to use, run “show version” from the CLI and refer to the “Architecture” Field. Version: 1.0 URL: SecurityAdvisory88_CVE-2023-3646_Hotfix_i686.swix https://www.arista.com/support/advisories-notices/sa-download/ SWIX hash:(SHA-512) 9c01d1bc1d657879e1a1b657a8c0dab090d589efc3f2c64e9cac1ae0356fce14496809893bffb0892b1505f8b4ee25cad0064bd7315ba6737dc5fdb200539f1a   URL: SecurityAdvisory88_CVE-2023-3646_Hotfix_x86_64.swix https://www.arista.com/support/advisories-notices/sa-download/ SWIX hash:(SHA512) 98e98c2c34f81df4da3e4068ac9a81191f4c6ef1acab884972d092c79a7495e00d9a25c8713620d3e25b4699f777810a627634eb8078dcbbb19317ed27a9b0d5   For instructions on installation and verification of the hotfix patch, refer to the “managing eos extensions” https://www.arista.com/en/um-eos/eos-managing-eos-extensions  section in the EOS User Manual. Ensure that the patch is made persistent across reboots by running the command ‘copy installed-extensions boot-extensions’.

Mirroring to multiple destinations must be configured: switch(config)#show monitor session Session s1 ------------------------ Sources: Both Interfaces:       Et1/1 Destination Ports:     Et9/1 : active     Et10/1 : active In the above example two destinations, Et9/1 and Et10/1, are configured. Mirroring config must be added with mirror destination being ethernet port, example: switch # show running-config | section monitor monitor session APCON destination Ethernet54/1 In the above example the argument after destination is an Ethernet port.

The suggestion to prevent this issue is to remove any mirroring config #show monitor session No sessions created This example confirms that the system does not have any mirroring config present which will prevent this issue from occurring.