title: This advisory documents the impact of an internally found vulnerability in Arista EOS for security ACL bypass.  The impact of this vulnerability is that the security ACL drop rule might be bypassed if a NAT ACL rule filter with permit action matches t ...
description: This advisory documents the impact of an internally found vulnerability in Arista EOS for security ACL bypass. The impact of this vulnerability is that the security ACL drop rule might be bypassed if a NAT ACL rule filter with permit action matches the packet flow. This could allow a host with an IP address in a range that matches the range allowed by a NAT ACL and a range denied by a Security ACL to be forwarded incorrectly as it should have been denied by the Security ACL. This can enable an ACL bypass.
problem types: CWE-284 Improper Access Control
affected:
{
product: EOS
vendor: Arista Networks
versions:
lessThanOrEqual: 4.24.9, status: affected, version: 4.24.0, versionType: custom
lessThanOrEqual: 4.25.8, status: affected, version: 4.25.0, versionType: custom
lessThanOrEqual: 4.26.5, status: affected, version: 4.26.0, versionType: custom
lessThanOrEqual: 4.27.3, status: affected, version: 4.27.0, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: NONE
baseScore: 5.8
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: LOW
privilegesRequired: NONE
scope: CHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
version: 3.1
]
solutions: The recommended resolution is to upgrade to a remediated software version at your earliest convenience.
The fixed versions for the currently supported release trains are as follows:
4.24.10 and later releases in the 4.24.x train
4.25.9 and later releases in the 4.25.x train
4.26.6 and later releases in the 4.26.x train
4.27.4 and later releases in the 4.27.x train
4.28.0 and later releases in the 4.28.x train
workarounds: Configure a NAT “drop” ACL rule for each security ACL “drop” rule that should be applied to the interface that has NAT configured. This will prevent the packets from being translated at the expense of maintaining the configuration in two places.