CVE-2026-73445
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
Summary
On affected platforms running Arista EOS, an issue with the gRPC Network Security Interface (gNSI) Authz Rotate RPC may cause an incorrect Authz policy which was uploaded in the ongoing RPC stream to become active. This does not affect Bootz.
This issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Arista Networks | EOS | 4.36.0F <= 4.36.0.1F | affected |
| Arista Networks | EOS | 4.35.0F <= 4.35.5M | affected |
| Arista Networks | EOS | 4.34.0F <= 4.34.7M | affected |
| Arista Networks | EOS | 4.33.0F <= 4.33.8M | affected |
| Arista Networks | EOS | 4.32.0F < 4.33.0F | affected |
| Arista Networks | EOS | 4.31.0F < 4.32.0F | affected |
Weaknesses
- CWE-20: CWE-20 Improper Input Validation
Workarounds
Include exactly one UploadRequest in a gNSI Authz Rotate request.
Use a gNSI Authz policy that restricts gNSI Authz use to only those who strictly need it. Below is an example policy that only allows user "Neo" to rotate Authz policies:
{ "name":"restrict-authz-policy", "allow_rules":[ { "name":"neoallow", "request":{ "paths":[ "/gnsi.authz.v1.Authz/Rotate" ], "headers":[ { "key":"username", "values":[ "Neo" ] } ] } }, { "name":"allow-gnmi", "request":{ "paths":[ "/gnmi.gNMI/" ] } }, { "name":"allow-gnoi", "request":{ "paths":[ "/gnoi." ] } } ] }
Ideally, this policy would be uploaded via a gNSI client for correct version and created-on metadata handling. However, the policy can also be written directly to the active policy file:
switch#bash timeout 100 echo "{"name":"restrict-authz-policy","allow_rules":[{"name":"neoallow","request":{"paths":["/gnsi.authz.v1.Authz/Rotate"],"headers":[{"key":"username","values":["Neo"]}]}},{"name":"allow-gnmi","request":{"paths":["/gnmi.gNMI/"]}},{"name":"allow-gnoi","request":{"paths":["/gnoi."]}}]}" | sudo tee /persist/sys/gnsi/authz/policy.json && sleep 11
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: no
- Technical Impact: partial
References
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.