# CVE-2024-9135: Memory corruption in EOS

> A memory leak in Arista EOS BGP Link State allows remote attackers to cause denial of service via BGP peer flaps.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 4 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-wqvf-m58c-h7rw

## What is CVE-2024-9135?

CVE-2024-9135 is a medium-severity memory corruption vulnerability in Arista Networks EOS, published on 4 Mar 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 BGP Link State configured, BGP peer flap can cause the BGP agent to leak memory. This may result in BGP routing processing being terminated and route flapping.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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


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

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

## Is CVE-2024-9135 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9135 is a medium-severity memory corruption vulnerability in Arista Networks EOS, published on 4 Mar 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-9135 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-9135/ (Markdown: https://insights.sbomify.com/CVE-2024-9135/index.md)
```

## Sources

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

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