CVE-2022-27642
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 bypass authentication 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 httpd service. The issue results from incorrect string matching logic when accessing protected pages. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-15854.
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 confidenceAuthentication bypass vulnerability in NETGEAR R6700v3 routers (firmware 1.0.4.120_10.0.91) in the httpd service. The flaw involves incorrect string matching logic when accessing protected pages, allowing network-adjacent attackers to bypass authentication without credentials. This can be chained with other vulnerabilities for root code execution.
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< 2.1.3.7< 1.1.6.34< 1.1.6.124< 1.1.6.14< 1.1.6.124< 1.1.6.14< 1.0.1.78< 1.0.4.126< 1.0.4.126CVSS 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 modelLocate the model number on the router device label or check the web interface for the exact model (CAX80, LAX20, MR60, MR80, MS60, MS80, R6400, or R6700)Affected if Model is not one of the listed affected models, then likely not vulnerable to this specific CVE
-
Check installed firmware versionAccess router web interface, navigate to Administration > Firmware Update or similar, or check the version displayed on the login page or in settings. Compare against: CAX80 < 2.1.3.7, LAX20 < 1.1.6.34, MR60 < 1.1.6.124, MR80 < 1.1.6.14, MS60 < 1.1.6.124, MS80 < 1.1.6.14, R6400 < 1.0.1.78 or < 1.0.4.126, R6700 < 1.0.4.126Affected if Firmware version is lower than the version thresholds listed for your specific model
-
Verify httpd service accessibilityAttempt to access the router management web interface (httpd) from a network-adjacent position by navigating to the router's IP address in a browser. Check if the login page or administrative pages are reachable without authenticationAffected if The httpd service is exposed and responds to requests, especially if management interface is accessible from WAN or untrusted networks
-
Confirm management interface exposureCheck router firewall settings to determine if the web management interface is accessible from WAN (internet) side. Look for settings like 'Allow remote management' or 'Web management port' in the router's security or administration settingsAffected if Remote management is enabled and the httpd port (typically 80/443) is exposed to untrusted networks, making the authentication bypass exploitable from outside the local network
You are affected if your router model matches one of the affected models AND your installed firmware version is below the specified threshold AND the httpd management interface is accessible to network-adjacent attackers.
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.1.6.14
Apply available NETGEAR firmware patch; if unavailable, implement network segmentation to restrict unauthorized access to the router management interface.
Upgrade to firmware version 2.1.3.7 or later (Cax80), 1.1.6.34 or later (Lax20), 1.1.6.124 or later (Mr60/Ms60), 1.1.6.14 or later (Mr80/Ms80), 1.0.1.78 or later / 1.0.4.126 or later (R6400), 1.0.4.126 or later (R6700)
- 1. Identify your exact NETGEAR router model (e.g., R6700, R6400, Cax80, Lax20, Mr60, Mr80, Ms60, Ms80)
- 2. Check the current firmware version by logging into the router web interface and navigating to Administration > Firmware Update > Check for New Version
- 3. Download the latest firmware for your specific model from the official NETGEAR support website (support.netgear.com)
- 4. In the router web interface, go to Administration > Firmware Update > Manual Update
- 5. Click Browse/Choose File and select the downloaded firmware file
- 6. Click Upload and wait for the firmware to be applied - do not power off the router during this process
- 7. After the router reboots, log back into the web interface and verify the new firmware version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27642 — 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-27642 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