ACL bypass via ignored IP protocol matching
Published Apr 14, 2022 · Updated Sep 16, 2024
Improper access control in Arista EOS 4.26.3M and earlier and 4.27.0F allows remote attackers to bypass IPv4 ACL protocol filters. When a VXLAN rule occurs in an ingress IPv4 ACL, EOS programs that rule and every later rule without enforcing the configured IP protocol field. The issue requires an affected switch with a TCAM profile enabled and such an ACL active on ingress, permitting IP traffic that the ACL was intended to filter.
Summary
What happened
Improper access control in Arista EOS 4.26.3M and earlier and 4.27.0F allows remote attackers to bypass IPv4 ACL protocol filters. When a VXLAN rule occurs in an ingress IPv4 ACL, EOS programs that rule and every later rule without enforcing the configured IP protocol field. The issue requires an affected switch with a TCAM profile enabled and such an ACL active on ingress, permitting IP traffic that the ACL was intended to filter.
The record
- CVE
- CVE-2021-28505
- Published
- Apr 14, 2022
- Updated
- Sep 16, 2024
- Vendor
- Arista Networks
- Product
- Arista EOS
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.26.3M <=4.26.0
- Affected versionversion=4.27.0F <=4.27.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo