# CVE-2024-8000: Security feature bypass in EOS

> Incomplete ACL installation after restart allows bypassing 802.1X security controls on Arista EOS devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-8fjr-734h-7jj5

## What is CVE-2024-8000?

CVE-2024-8000 is a medium-severity vulnerability in Arista Networks EOS, published on 4 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On affected platforms running Arista EOS with 802.1X configured, certain conditions may occur where a dynamic ACL is received from the AAA server resulting in only the first line of the ACL being installed after an Accelerated Software Upgrade (ASU) restart. 

Note: supplicants with pending captive-portal authentication during ASU would be impacted with this bug.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2024-8000?


## How do I fix CVE-2024-8000?

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

## Is CVE-2024-8000 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8000 and fix it if it is affected.

What it is: CVE-2024-8000 is a medium-severity vulnerability in Arista Networks EOS, published on 4 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8000 in the wild and no public exploit code.

Affected product: Arista Networks EOS. 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-2024-8000/ (Markdown: https://insights.sbomify.com/CVE-2024-8000/index.md)
```

## Sources

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

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