# CVE-2020-11622: Denial of service in n/a

> Attackers can cause a denial of service in Arista Cloud EOS VM routers when TCP MSS options are configured.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-536w-ccgx-f4pc

## What is CVE-2020-11622?

CVE-2020-11622 is a high-severity denial of service vulnerability in n/a, published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in Arista’s Cloud EOS VM / vEOS 4.23.2M and below releases in the 4.23.x train, 4.22.4M and below releases in the 4.22.x train, 4.21.3M to 4.21.9M releases in the 4.21.x train, 4.21.3FX-7368.*, 4.21.4-FCRFX.*, 4.21.4.1, 4.21.7.1, 4.22.2.0.1, 4.22.2.2.1, 4.22.3.1, and 4.23.2.1 Router code in a scenario where TCP MSS options are configured.

## Which versions are affected by CVE-2020-11622?

It affects 2 products.


Products: Arista Cloudeos, Arista Veos.

## How do I fix CVE-2020-11622?

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

## Is CVE-2020-11622 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-24545](https://insights.sbomify.com/CVE-2023-24545/): Denial of service in EOS (high 7.5)
- [CVE-2023-24513](https://insights.sbomify.com/CVE-2023-24513/): Denial of service in EOS (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11622 and fix it if it is affected.

What it is: CVE-2020-11622 is a high-severity denial of service vulnerability in n/a, published on 10 Jun 2020. 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-2020-11622 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-2020-11622/ (Markdown: https://insights.sbomify.com/CVE-2020-11622/index.md)
```

## Sources

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

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