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
Advisories
Source ID Title
EUVD 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
Fixes

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


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

History

Mon, 03 Feb 2025 20:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Arista

Published:

Updated: 2025-02-03T19:15:59.467Z

Reserved: 2023-01-24T00:00:00.000Z

Link: CVE-2023-24512

cve-icon Vulnrichment

Updated: 2024-08-02T10:56:04.371Z

cve-icon NVD

Status : Modified

Published: 2023-04-25T21:15:10.190

Modified: 2024-11-21T07:48:01.437

Link: CVE-2023-24512

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.