# CVE-2021-22909: Other in EdgeMAX EdgeRouter

> Attackers can intercept firmware updates to inject malicious code, compromising EdgeMAX EdgeRouter devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rcxg-wqw2-89wf

## What is CVE-2021-22909?

CVE-2021-22909 is a high-severity vulnerability in EdgeMAX EdgeRouter, published on 27 May 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability found in EdgeMAX EdgeRouter V2.0.9 and earlier could allow a malicious actor to execute a man-in-the-middle (MitM) attack during a firmware update. This vulnerability is fixed in EdgeMAX EdgeRouter V2.0.9-hotfix.1 and later.

Weakness: CWE-295 (Improper Certificate Validation), CWE-300 (Channel Accessible by Non-Endpoint)

## Which versions are affected by CVE-2021-22909?

It affects 1 product.


Products: Ui Edgemax Edgerouter Firmware.

## How do I fix CVE-2021-22909?

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

## Is CVE-2021-22909 being exploited?

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

## Other vulnerabilities in EdgeMAX EdgeRouter

- [CVE-2022-43553](https://insights.sbomify.com/CVE-2022-43553/): Privilege escalation in EdgeMAX EdgeRouter (high 8.8)
- [CVE-2023-2373](https://insights.sbomify.com/CVE-2023-2373/): Ubiquiti EdgeRouter X Web Management command injection (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22909 and fix it if it is affected.

What it is: CVE-2021-22909 is a high-severity vulnerability in EdgeMAX EdgeRouter, published on 27 May 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-22909 in the wild and no public exploit code.

Affected product: EdgeMAX EdgeRouter. 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-2021-22909/ (Markdown: https://insights.sbomify.com/CVE-2021-22909/index.md)
```

## Sources

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

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