First published: Tue Mar 04 2025(Updated: )
On affected platforms running Arista EOS with 802.1X configured, certain conditions may occur where a dynamic ACL is received from the AAA server resulting in only the first line of the ACL being installed after an Accelerated Software Upgrade (ASU) restart. Note: supplicants with pending captive-portal authentication during ASU would be impacted with this bug.
Credit: psirt@arista.com
Affected Software | Affected Version | How to fix |
---|---|---|
Arista EOS |
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-2024-8000 has been fixed in the following releases: * 4.33.0M and above * 4.32.5M and above releases in the 4.32.x train * 4.31.6M and above releases in the 4.31.x train * 4.30.9M and above releases in the 4.30.x train
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8000 has a severity rating that indicates a medium-level impact on network security due to potential misconfiguration of ACLs.
To mitigate CVE-2024-8000, ensure proper configuration and management of ACLs after performing an Accelerated Software Upgrade on Arista EOS.
CVE-2024-8000 affects platforms running Arista EOS with 802.1X configured.
CVE-2024-8000 is triggered when a dynamic ACL is received from the AAA server during specific conditions after an ASU restart.
Yes, regularly verify ACL installation and apply configurations to ensure all lines of the dynamic ACL are properly installed.