dbcve.org
Extensible Operating SystemOperating system · Arista

CVE-2019-14810

MEDIUM · 5.9 CVSS v3.1 Published 2019-10-10
Fix available
A fix is available. Upgrade to after 4.21.7 or later.
See remediation →
68/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
A vulnerability has been found in the implementation of the Label Distribution Protocol (LDP) protocol in EOS. Under race conditions, the LDP agent can establish an LDP session with a malicious peer potentially allowing the possibility of a Denial of Service (DoS) attack on route updates and in turn potentially leading to an Out of Memory (OOM) condition that is disruptive to traffic forwarding. Affected EOS versions include: 4.22 release train: 4.22.1F and earlier releases 4.21 release train: 4.21.0F - 4.21.2.3F, 4.21.3F - 4.21.7.1M 4.20 release train: 4.20.14M and earlier releases 4.19 release train: 4.19.12M and earlier releases End of support release trains (4.18 and 4.17)

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 · high confidence

A race condition vulnerability exists in Arista EOS's Label Distribution Protocol (LDP) implementation. The LDP agent can incorrectly establish sessions with malicious peers, allowing an attacker to trigger route update disruptions that can cause an Out of Memory condition, disrupting traffic forwarding.

MitigationUpgrade to a patched EOS version. As a temporary measure, implement network segmentation and filter LDP traffic to only trusted peers.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Extensible Operating SystemOperating system
Affected:>= 4.19, <= 4.19.12m>= 4.20, <= 4.20.14m>= 4.21.0f, <= 4.21.2.3f>= 4.21.3f, <= 4.21.7= 4.17= 4.18= 4.22.1f

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 LDP protocol is enabled on the device
    Run 'show ldp status' or 'show mpls ldp' command in EOS CLI to verify if Label Distribution Protocol is configured and running
    Affected if LDP is enabled and the device has LDP peers configured - the vulnerability only affects devices actively using LDP
  2. Identify the installed EOS version
    Run 'show version' command to display the EOS software version running on the device
    Affected if The installed version falls within any of these ranges: 4.17, 4.18, 4.19 through 4.19.12m, 4.20 through 4.20.14m, 4.21.0f through 4.21.2.3f, 4.21.3f through 4.21.7, or 4.22.1f
  3. Check for LDP peer connections
    Run 'show ldp neighbor' or 'show mpls ldp neighbor' to list established LDP peer sessions
    Affected if The device has active LDP neighbor relationships - the race condition can be triggered by malicious peers establishing sessions
  4. Verify LDP transport configuration
    Run 'show ldp parameters' or check LDP transport address configuration to confirm how LDP sessions are established
    Affected if LDP is configured to accept connections from untrusted sources - the vulnerability allows malicious peers to incorrectly establish sessions

The device is affected if LDP is enabled AND the EOS version matches one of the vulnerable version ranges listed in the CVE, because the race condition can then be exploited by malicious LDP peers to trigger OOM conditions.

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
Upgrade available Upgrade to a release after 4.21.7
Interim mitigation

Upgrade to a patched EOS version. As a temporary measure, implement network segmentation and filter LDP traffic to only trusted peers.

Fix this in Extensible Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14810 — 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-2019-14810 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