# CVE-2019-14810: Race condition in n/a

> A race condition in the LDP protocol allows a malicious peer to cause a Denial of Service via memory exhaustion, affecting Arista EOS network devices.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-488w-r5hp-hwch

## What is CVE-2019-14810?

CVE-2019-14810 is a medium-severity vulnerability in n/a, published on 10 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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)

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2019-14810?

It affects 1 product.


Products: Arista Extensible Operating System.

## How do I fix CVE-2019-14810?

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

## Is CVE-2019-14810 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14810 and fix it if it is affected.

What it is: CVE-2019-14810 is a medium-severity vulnerability in n/a, published on 10 Oct 2019. 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-2019-14810 in the wild and no public exploit code.

Affected product: n/a. 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-2019-14810/ (Markdown: https://insights.sbomify.com/CVE-2019-14810/index.md)
```

## Sources

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

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