First published: Tue Mar 04 2025(Updated: )
On affected platforms running Arista EOS with OpenConfig configured, a gNOI request can be run when it should have been rejected. This issue can result in users retrieving data that should not have been available
Credit: psirt@arista.com
Affected Software | Affected Version | How to fix |
---|---|---|
Arista EOS |
The recommended resolution 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. For more information about upgrading see EOS User Manual: Upgrades and Downgrades https://www.arista.com/en/um-eos/eos-upgrades-and-downgrades CVE-2025-1259 is fixed in the following releases: * 4.33.2 and later releases in the 4.33.x train * 4.32.4 and later releases in the 4.32.x train * 4.31.6 and later releases in the 4.31.x train * 4.30.9 and later releases in the 4.30.x train * 4.29.10 and later releases in the 4.29.x train * 4.28.13 and later releases in the 4.28.x train
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-1259 is classified as a medium severity vulnerability affecting Arista EOS.
To fix CVE-2025-1259, update Arista EOS to the latest version provided in the security advisory.
CVE-2025-1259 allows unauthorized access to data through gNOI requests, potentially exposing sensitive information.
CVE-2025-1259 affects platforms running Arista EOS with OpenConfig configured.
Currently, there are no known workarounds for CVE-2025-1259, so updating the software is recommended.