# CVE-2025-0505: Privilege escalation in CloudVision Portal

> Attackers can exploit Zero Touch Provisioning to gain excessive admin privileges on Arista CloudVision systems, allowing them to query or manipulate managed device states.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-v3m4-v33x-7jhp

## What is CVE-2025-0505?

CVE-2025-0505 is a critical vulnerability in Arista Networks CloudVision Portal, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Arista CloudVision systems (virtual or physical on-premise deployments), Zero Touch Provisioning can be used to gain admin privileges on the CloudVision system, with more permissions than necessary, which can be used to query or manipulate system state for devices under management. Note that CloudVision as-a-Service is not affected.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-0505?


## How do I fix CVE-2025-0505?

No fix has been published for CVE-2025-0505 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0505 being exploited?

There is no known exploitation of CVE-2025-0505 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0505 and fix it if it is affected.

What it is: CVE-2025-0505 is a critical vulnerability in Arista Networks CloudVision Portal, published on 8 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0505 in the wild and no public exploit code.

Affected product: Arista Networks CloudVision Portal. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0505/ (Markdown: https://insights.sbomify.com/CVE-2025-0505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0505
- OSV: https://osv.dev/vulnerability/CVE-2025-0505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0505/
Summaries are generated and may contain mistakes; the official description above is the record.