Arista Networks EOS
Security Advisory 0164
On affected platforms running Arista EOS, if OpenConfig is configured and running a gNMI server on the system, and if gNSI Pathz is configured and a gNSI Pathz policy is present on the system, then gNMI may fail to correctly enforce the rules in this policy if both a group rule and a user rule for the same path is present in the policy. Under certain conditions, this can lead to an authenticated user gaining unauthorized permission to read or write gNMI paths that the Pathz policy is intended to restrict.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.33.2F, <= 4.33.8M
- >= 4.34.0F, <= 4.34.6M
- >= 4.35.0F, <= 4.35.5M
- >= 4.36.0F, <= 4.36.0.1F
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.7M 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
Option 1: Disable gNSI Pathz entirely: switch#configure switch(config)#management api gnsi switch(config-mgmt-api-gnsi)#no service pathz Option 2: Push a new gNSI Pathz policy that does not contain any group rules, using only user-principal rules. To push a new policy via grpcurl: grpcurl -protoset ./pathz.proto.pb -H 'username:$USER' -v -d @ -plaintext $TARGET:$PORT gnsi.pathz.v1.Pathz/Rotate << EOF { "upload_request": { "version": "<version>", "created_on": <timestamp>, "policy": <policy> } } { "finalize_rotation": {} } EOF Ensure all rules in the policy use "user" as the principal rather than "group" to avoid triggering this vulnerability.
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.