CVE-2022-27643
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 · uneditedThis 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.
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 confidenceA buffer overflow vulnerability in the SOAPAction header parsing of NETGEAR R6700v3 routers allows remote, unauthenticated attackers on the adjacent network to execute arbitrary code as root due to improper length validation when copying user-supplied data to a fixed-size buffer.
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< 1.0.1.78< 1.0.4.126< 1.0.4.126< 1.3.3.148< 1.0.11.134< 1.3.3.148< 1.0.5.84< 1.4.3.88< 1.4.3.88CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLog into the router web interface (typically 192.168.1.1) and check the Device Info or Administration page to confirm the exact model number (e.g., R6700, R7000, R6400, etc.)Affected if The model is any of the following: R6400, R6700, R6900p, R7000, R7000p, R7850, R7900p, or R7960p
-
Determine the installed firmware versionIn the router web interface, navigate to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version installedAffected if The firmware version is below the safe threshold for your model (R6400: < 1.0.1.78 or < 1.0.4.126; R6700: < 1.0.4.126; R6900p/R7000p: < 1.3.3.148; R7000: < 1.0.11.134; R7850: < 1.0.5.84; R7900p/R7960p: < 1.4.3.88)
-
Verify the SOAP/UPnP service is accessibleFrom a host on the same network, attempt to access the UPnP service on the router (port 1900/TCP or 5000/TCP) using a tool like upnp-inspector or by sending an HTTP request to the SOAP endpointAffected if The SOAP service responds to requests from the adjacent network, indicating the vulnerable parsing code is reachable
You are affected if you own one of the listed Netgear models AND your firmware version is below the safe threshold AND the SOAP/UPnP service is accessible from your network.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped1.0.1.781.0.4.1261.0.5.84
Apply vendor-supplied firmware updates from NETGEAR; if unavailable, restrict network access to the device's management interface and consider replacing the end-of-life hardware.
R6400: 1.0.1.78 (or 1.0.4.126 and above); R6700: 1.0.4.126 and above; R6900p: 1.3.3.148 and above; R7000: 1.0.11.134 and above; R7000p: 1.3.3.148 and above; R7850: 1.0.5.84 and above; R7900p: 1.4.3.88 and above; R7960p: 1.4.3.88 and above
- 1. Identify your router model number (R6400, R6700, R6900p, R7000, R7000p, R7850, R7900p, or R7960p)
- 2. Navigate to the NETGEAR support page (support.netgear.com) and locate the firmware download section for your specific model
- 3. Download the latest firmware version that addresses CVE-2022-27643
- 4. Access your router's web management interface (typically at 192.168.1.1)
- 5. Navigate to the Administration > Firmware Update section
- 6. Select the downloaded firmware file and initiate the update
- 7. Wait for the update to complete and the router to reboot
- 8. Verify the new firmware version matches the patched version in the release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27643 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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