# CVE-2024-5872: Denial of service in EOS

> Crafted packets with incorrect VLAN tags can cause control plane instability and route flaps on Arista EOS network devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2025
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-wq57-x73w-8875

## What is CVE-2024-5872?

CVE-2024-5872 is a medium-severity denial of service vulnerability in Arista Networks EOS, published on 10 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On affected platforms running Arista EOS, a specially crafted packet with incorrect VLAN tag might be copied to CPU, which may cause incorrect control plane behavior related to the packet, such as route flaps, multicast routes learnt, etc.

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


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

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

## Is CVE-2024-5872 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5872 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5872 is a medium-severity denial of service vulnerability in Arista Networks EOS, published on 10 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5872 exists.

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-5872/ (Markdown: https://insights.sbomify.com/CVE-2024-5872/index.md)
```

## Sources

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

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