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

> Attackers can bypass Traffic Policy drop rules on Arista EOS by sending untagged packets, causing unintended packet forwarding to unexpected destinations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 25 Aug 2025
- **Also known as:** GHSA-vjv2-pp4x-76x9

## What is CVE-2024-9448?

CVE-2024-9448 is a high-severity vulnerability in Arista Networks EOS, 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 affected platforms running Arista EOS with Traffic Policies configured the vulnerability will cause received untagged packets not to hit Traffic Policy rules that they are expected to hit. If the rule was to drop the packet, the packet will not be dropped and instead will be forwarded as if the rule was not in place. This could lead to packets being delivered to unexpected destinations.

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

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


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

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

## Is CVE-2024-9448 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9448 is a high-severity vulnerability in Arista Networks EOS, 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-2024-9448 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-9448/ (Markdown: https://insights.sbomify.com/CVE-2024-9448/index.md)
```

## Sources

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

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