CVE-2022-27641
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 NetUSB module. The issue results from the lack of proper validation of user-supplied data, which can result in an integer overflow before allocating a buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15806.
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 confidenceInteger overflow in NetUSB module of NETGEAR R6700v3 routers (firmware 1.0.4.120_10.0.91) allows unauthenticated network-adjacent attackers to execute arbitrary code as root via improper validation of user-supplied data before buffer allocation.
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.68< 1.0.1.90< 1.0.1.240< 1.1.0.112< 1.1.0.112< 1.0.4.122< 1.0.4.122< 1.0.11.130CVSS 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 your router modelCheck the product label on the router bottom or the admin interface (typically at 192.168.1.1 or 192.168.0.1) for the exact model number (e.g., R6700v3, R7000, D7800, etc.)Affected if The model matches one of the affected models: D7800, Ex6200, Ex8000, R6220, R6230, R6400, R6700, R6700v3, or R7000
-
Check the installed firmware versionLog into the router admin interface and navigate to the Administration or Router Status page to view the current firmware version numberAffected if The firmware version is below the threshold for your model: D7800 < 1.0.1.68, Ex6200 < 1.0.1.90, Ex8000 < 1.0.1.240, R6220 < 1.1.0.112, R6230 < 1.1.0.112, R6400 < 1.0.4.122, R6700 < 1.0.4.122, R6700v3 = 1.0.4.120_10.0.91, R7000 < 1.0.11.130
-
Verify if NetUSB service is enabledIn the router admin interface, look for USB or NetUSB settings (usually under Advanced, USB, or Storage settings) to see if the NetUSB feature is turned onAffected if NetUSB is enabled and the firmware version is in the affected range; the vulnerability requires NetUSB to be active for exploitation
You are affected if your router model is one of the listed models, your firmware version is below the specified threshold for that model, and NetUSB service is enabled.
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.681.0.1.901.0.1.240
Apply vendor firmware patch when available; until then, restrict network access to the router's management interface and disable NetUSB service if possible.
D7800: 1.0.1.68 or later | Ex6200: 1.0.1.90 or later | Ex8000: 1.0.1.240 or later | R6220: 1.1.0.112 or later | R6230: 1.1.0.112 or later | R6400: 1.0.4.122 or later | R6700: 1.0.4.122 or later | R7000: 1.0.11.130 or later
- 1. Identify your NETGEAR router model from the list: D7800, Ex6200, Ex8000, R6220, R6230, R6400, R6700, or R7000
- 2. Access the router's web management interface by entering the router's IP address in a web browser
- 3. Log in with administrator credentials
- 4. Navigate to the 'Administration' or 'Advanced' settings section
- 5. Look for 'Firmware Update' or 'Router Update' option
- 6. Check the current firmware version under 'Router Status' or similar
- 7. If the firmware version is below the fixed version for your model, download the latest firmware from the official NETGEAR support website (kb.netgear.com)
- 8. In the firmware update section, click 'Upload' or 'Browse' to select the downloaded firmware file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27641 — 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-27641 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