CVE-2022-27644
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 compromise the integrity of downloaded information 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 downloading of files via HTTPS. The issue results from the lack of proper validation of the certificate presented by the server. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-15797.
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 confidenceNETGEAR R6700v3 routers running firmware 1.0.4.120_10.0.91 have a certificate validation vulnerability in the HTTPS file download functionality. The lack of proper validation of the server's SSL/TLS certificate allows network-adjacent attackers to perform man-in-the-middle attacks, compromising the integrity of downloaded information. This can be chained with other vulnerabilities to achieve arbitrary code execution as root.
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.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.0.4.84CVSS 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 router modelAccess the router admin web interface or check the device label to confirm the exact model number (e.g., R6400, R6700, R6900p, R7000, R7000p, R7850, R7960p, R8000)Affected if The router model is any of the eight affected models listed in the CVE
-
Check installed firmware versionLog into the router admin panel (typically at 192.168.1.1), navigate to Administration > Firmware Update or Router Status page, and record the displayed firmware version numberAffected if The installed firmware version is below the threshold for your model: R6400/R6700 < 1.0.4.126, R6900p/R7000p < 1.3.3.148, R7000 < 1.0.11.134, R7850 < 1.0.5.84, R7960p < 1.4.3.88, R8000 < 1.0.4.84
-
Locate HTTPS file download featureIn the router admin interface, look for sections labeled File Download, Remote Management, USB Storage settings, or Network Discovery that allow downloading configuration files or firmware updates over HTTPS from an external serverAffected if The router has an HTTPS file download or remote access feature that accepts URLs to external servers
-
Verify certificate validation behaviorIf possible, use a network proxy to intercept HTTPS traffic from the router when the file download feature is used, and observe whether the router accepts self-signed or invalid certificates without rejecting the connectionAffected if The router accepts SSL/TLS certificates that are expired, self-signed, or have mismatched hostnames during HTTPS file download operations
A user is affected if they own one of the eight listed Netgear router models AND the installed firmware version is below the specified threshold for that model, with the HTTPS file download feature accessible on their device.
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.4.841.0.4.1261.0.5.84
Apply the vendor-supplied firmware update when available. As a compensating control, isolate affected devices on restricted network segments to limit exposure to adjacent attackers.
Router-specific firmware: R6400/R6700 to 1.0.4.126, R6900p/R7000p to 1.3.3.148, R7000 to 1.0.11.134, R7850 to 1.0.5.84, R7960p to 1.4.3.88, R8000 to 1.0.4.84
- 1. Identify your NETGEAR router model from the affected list (R6400, R6700, R6900p, R7000, R7000p, R7850, R7960p, R8000).
- 2. Access the router's web interface by navigating to routerlogin.net or 192.168.1.1.
- 3. Log in with your administrator credentials.
- 4. Navigate to the Administration > Firmware Update section or check under Advanced > Administration > Firmware Update.
- 5. Download the appropriate firmware version for your specific model from the NETGEAR support website (kb.netgear.com).
- 6. Upload and install the firmware file, or enable automatic update if available.
- 7. After the firmware update completes, verify the router is running the fixed version: R6400/R6700 should be at 1.0.4.126, R6900p/R7000p at 1.3.3.148, R7000 at 1.0.11.134, R7850 at 1.0.5.84, R7960p at 1.4.3.88, R8000 at 1.0.4.84.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27644 — 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-27644 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