Arista Networks EOS
Security Advisory 0163
On affected EOS platforms with AAA-based gRPC authorization enabled for OpenConfig, gRPC requests of an authenticated user to OpenConfig may use the wrong privilege level, resulting in an authorization using the wrong AAA method list. This does not impact non-gRPC OpenConfig requests such as NETCONF.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.29.0F, < 4.30.0F
- >= 4.30.0F, < 4.31.0F
- >= 4.31.0F, < 4.32.0F
- >= 4.32.0F, <= 4.32.11M
- >= 4.33.0F, <= 4.33.8M
- >= 4.34.0F, <= 4.34.7M
- >= 4.35.0F, <= 4.35.5M
- >= 4.36.0F, <= 4.36.0.1F
Fixed in 4.30.0F, 4.31.0F, 4.32.0F
Mitigation
The following EOS releases contain the fix for this vulnerability: - 4.33.9M and later releases in the 4.33.x train - 4.34.8M and later releases in the 4.34.x train - 4.35.6M and later releases in the 4.35.x train - 4.36.1F and later releases in the 4.36.x train No hotfix is available for this vulnerability.
Workaround
Ensure that the privilege level 0 AAA authorization method list includes methods beyond 'none' to prevent unintended access escalation: aaa authorization exec default local group tacacs+ aaa authorization commands 0 default local group tacacs+ To detect potential exploitation, enable AAA accounting and monitor logs for cases where a user's privilege level in gRPC requests does not match their defined privilege level (e.g., a user with privilege 9 appearing as priv-lvl=0 in gRPC requests).
References
- Vendor advisory arista.com/en/support/advisories-notices/secur…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.