dbcve.org
Memory LeakWeakness · CWE-401

CVE-2024-9135

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a memory leak vulnerability in Arista EOS BGP agent that occurs when BGP Link State is configured. The vulnerability is triggered by BGP peer flap events, causing the BGP agent to leak memory. If the memory leak is severe enough, it can cause BGP routing processing to terminate, leading to route flapping.

MitigationIf BGP Link State is not required, disabling it removes the vulnerable code path. Otherwise, apply vendor-supplied patches when available and consider implementing BGP peer flap damping to reduce flap frequency.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Arista EOS device and version
    Run 'show version' to identify the EOS software version installed
    Affected if The device runs an unpatched Arista EOS version within the affected range
  2. Verify BGP is configured
    Run 'show ip bgp summary' or 'show bgp summary' to confirm BGP is running
    Affected if BGP is not configured - the vulnerability does not apply
  3. Check if BGP Link State is enabled
    Run 'show running-config | include link-state' or inspect BGP address-family configuration for the 'link-state' keyword
    Affected if BGP Link State is configured - this is the required condition for the vulnerability to be triggerable
  4. Look for BGP process memory issues or crashes
    Run 'show processes memory | include BGP' or check 'show log' for BGP process termination events
    Affected if BGP agent process shows excessive memory consumption or recent unexpected restarts

A user is affected if they are running a vulnerable Arista EOS version AND have BGP Link State configured, with BGP peer flaps occurring that trigger the memory leak.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If BGP Link State is not required, disabling it removes the vulnerable code path. Otherwise, apply vendor-supplied patches when available and consider implementing BGP peer flap damping to reduce flap frequency.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9135 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9135 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data