CVE-2021-28511: 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 ...
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.
Security readout for executives and security teams
Plain-English summary
CVE-2021-28511 is an Arista EOS ACL bypass issue. In affected configurations, traffic that should be blocked by a Security ACL may be forwarded if it also matches a NAT ACL permit rule. The business risk is unintended network access across controls that operators expect to enforce segmentation.
Executive priority
Treat this as a moderate network-control integrity issue. Prioritize environments using affected Arista EOS versions for segmentation, boundary filtering, or regulated network separation, especially where NAT and Security ACLs overlap.
Technical view
Arista describes an internally found EOS flaw where NAT ACL permit matching can override the intended Security ACL drop behavior for the same packet flow. The CVSS 3.1 score is 5.8 with network attack vector, low complexity, no privileges, no user interaction, scope changed, and low integrity impact.
Likely exposure
Exposure is limited to Arista EOS versions listed in the bundle: 4.24.0, 4.25.0, 4.26.0, and 4.27.0. Practical exposure depends on configurations where NAT ACL permit rules overlap traffic ranges denied by Security ACLs.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The described condition is configuration-dependent and could allow forwarding that violates intended ACL policy, but the provided sources do not prove public exploit activity.
Researcher notes
The evidence supports an ACL precedence or enforcement failure involving NAT ACL permit and Security ACL drop logic. The source bundle does not include fixed versions, workarounds, affected hardware scope, or exploit telemetry, so remediation details should be confirmed against the Arista advisory.
Mitigation direction
Review the Arista advisory for affected and fixed EOS release guidance.
Upgrade or apply vendor-recommended remediation once confirmed from Arista guidance.
Remove overlap between NAT ACL permit filters and Security ACL denied ranges where feasible.
Add upstream or downstream enforcement for denied traffic until EOS remediation is confirmed.
Validation and detection
Inventory Arista EOS devices running 4.24.0, 4.25.0, 4.26.0, or 4.27.0.
Review NAT ACL permit filters for overlap with Security ACL drop rules.
Validate policy enforcement in an authorized test environment without exposing production paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.