Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2024-8100

On affected versions of the Arista CloudVision Portal (CVP on-prem), the time-bound device onboarding token can be used to gain admin privileges on CloudVision.

High8.7EPSS 0.63%
Published
Updated
Reserved
Assigned by
Arista

Description

On affected versions of the Arista CloudVision Portal (CVP on-prem), the time-bound device onboarding token can be used to gain admin privileges on CloudVision.

Scores

CVSS scores of CVE-2024-8100, by who scored it
Scored byCVSSScoreVector
AristaCNA (assigner)3.1High8.7CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
NVDNVD · Deferred3.1High8.7CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.63% · top 50% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.7.

Weakness

Affected products

  • Arista Networks · CloudVision

    • affected 2024.3.0
    • affected 2024.0 – ≤ 2024.2
    • affected 2023.3.0 – ≤ 2023.3.1
    • affected 2023.0 – ≤ 2023.2
    • affected 2022
    • affected 2021
    • affected 2020
    • affected 2019
    • affected 2018

What to do

Solution: 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 CVP Software downloads https://www.arista.com/en/support/software-download   CVE-2024-8100 has been fixed in the following releases: * 2024.1.3 and later releases in the 2024.1.x train * 2024.2.2 and later releases in the 2024.2.x train * 2024.3.1 and later releases in the 2024.3.x train * 2025.1.0 and later releases in the 2025.1.x train

Workaround: Best practice is for generated device onboarding tokens to be valid for a limited time duration, and for the Device Onboarding permission which allows the generation of these tokens to only be granted to trusted users. Successful exploit generally requires one of the following: * A rogue or compromised internal user with Device enrollment read/write permissions OR,   * A valid device onboarding token that is easily accessible beyond the expected set of trusted users If all users with Device Onboarding privileges are trusted, and onboarding tokens are properly secured, then the risk of this issue is limited.

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-8100 badge
[![CVE-2024-8100](https://trackcve.app/badge/CVE-2024-8100.svg)](https://trackcve.app/cve/CVE-2024-8100)

Record last updated .