# CVE-2022-27643: Memory corruption in R6700v3

> Network-adjacent attackers can execute arbitrary code as root on NETGEAR R6700v3 routers via a buffer overflow in SOAP request handling.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-h8wj-xxvx-cv2r

## What is CVE-2022-27643?

CVE-2022-27643 is a high-severity memory corruption vulnerability in Netgear D6220 Firmware, published on 29 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700v3 1.0.4.120_10.0.91 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of SOAP requests. When parsing the SOAPAction header, the process does not properly validate the length of user-supplied data prior to copying it to a buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15692.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-27643?

It affects 27 products.


Products: Netgear D6220 Firmware, Netgear D6400 Firmware, Netgear D7000v2 Firmware, Netgear Dc112a Firmware, Netgear Ex3700 Firmware, Netgear Ex3800 Firmware, Netgear Ex6120 Firmware, Netgear Ex6130 Firmware, Netgear R6400 Firmware, Netgear R6700 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7100lg Firmware, Netgear R7850 Firmware, Netgear R7900p Firmware, Netgear R7960p Firmware, Netgear R8000 Firmware, Netgear R8000p Firmware, Netgear R8500 Firmware and 7 more.

## How do I fix CVE-2022-27643?

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

## Is CVE-2022-27643 being exploited?

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

## Other vulnerabilities in Netgear D6220 Firmware

- [CVE-2016-6277](https://insights.sbomify.com/CVE-2016-6277/): NETGEAR Multiple Routers Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2021-45527](https://insights.sbomify.com/CVE-2021-45527/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-45610](https://insights.sbomify.com/CVE-2021-45610/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-45638](https://insights.sbomify.com/CVE-2021-45638/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-34982](https://insights.sbomify.com/CVE-2021-34982/): NETGEAR Multiple Routers httpd Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27643 and fix it if it is affected.

What it is: CVE-2022-27643 is a high-severity memory corruption vulnerability in Netgear D6220 Firmware, published on 29 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-27643 in the wild and no public exploit code.

Affected product: Netgear D6220 Firmware. 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-2022-27643/ (Markdown: https://insights.sbomify.com/CVE-2022-27643/index.md)
```

## Sources

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

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