On affected platforms running Arista EOS, an authorized attacker with permissions to perform gNMI requests could craft a request allowing it to update arbitrary configurations in the switch.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Arista Networks | Terminattr | affected |
|
Configuration 1 [-]
| AND |
|
Configuration 2 [-]
|
No data.
No data available yet.
Vendor Solution
While the steps listed above resolve the issue, the recommended long term solution is to upgrade to a remediated software version at your earliest convenience. Arista recommends customers move to the latest version of each release that contains all the fixes listed below. There are two possible solutions: Upgrade the Streaming Telemetry Agent Customers can upgrade the Streaming Telemetry Agent to a fixed version, following the directions in https://arista.my.site.com/AristaCommunity/s/article/terminattr-upgrade-downgrade. Fixes are available in the following supported release trains: TerminAttr 1.25.0 and later Terminattr versions Users of 1.24.X and 1.23.X TerminAttr releases should upgrade to TerminAttr 1.25.0 or later. TerminAttr 1.22.2 and later version in the TerminAttr 1.22.X train TerminAttr 1.19.6 and later versions in the TerminAttr 1.19.X train
Vendor Workaround
The streaming telemetry agent can be configured in gRPC read-only mode by specifying -grpcreadonly as part of its configuration. For instance as follows: switch# daemon TerminAttr exec /usr/bin/TerminAttr -grpcreadonly -grpcaddr=... <other options...> no shutdown If TerminAttr is running, it must be restarted for the configuration to take effect. This can be done as follows: switch# daemon TerminAttr shutdown wait-for-warmup no shutdown
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-28530 | On affected platforms running Arista EOS, an authorized attacker with permissions to perform gNMI requests could craft a request allowing it to update arbitrary configurations in the switch. This situation occurs only when the Streaming Telemetry Agent (referred to as the TerminAttr agent) is enabled and gNMI access is configured on the agent. Note: This gNMI over the Streaming Telemetry Agent scenario is mostly commonly used when streaming to a 3rd party system and is not used by default when streaming to CloudVision |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.598% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|