dbcve.org
Cax80 FirmwareOperating system · Netgear

CVE-2022-27647

HIGH · 8.0 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 1.0.1.78 / 1.0.4.126 or later.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700v3 1.0.4.120_10.0.91 routers. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the handling of the name or email field provided to libreadycloud.so. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15874.

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 confidence

This vulnerability in NETGEAR R6700v3 routers (firmware 1.0.4.120_10.0.91) allows network-adjacent attackers with authenticated access to execute arbitrary code as root. The flaw exists in libreadycloud.so where the name or email field is not validated before being used in a system call. While authentication is required, the existing authentication mechanism can be bypassed.

MitigationApply the vendor-supplied firmware patch from NETGEAR for this vulnerability. If no patch is available, disable the readycloud functionality and restrict network access to the router's management interface.

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
Cax80 FirmwareOperating system
Affected:< 2.1.3.7
Lax20 FirmwareOperating system
Affected:< 1.1.6.34
Mr60 FirmwareOperating system
Affected:< 1.1.6.124
Mr80 FirmwareOperating system
Affected:< 1.1.6.14
Ms60 FirmwareOperating system
Affected:< 1.1.6.124
Ms80 FirmwareOperating system
Affected:< 1.1.6.14
R6400 FirmwareOperating system
Affected:< 1.0.1.78< 1.0.4.126
R6700 FirmwareOperating system
Affected:< 1.0.4.126

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Log into the router web management interface and locate the model number on the status or settings page, or check the physical device label
    Affected if Router model is one of: Cax80, Lax20, Mr60, Mr80, Ms60, Ms80, R6400, or R6700
  2. Check firmware version
    In the router web UI, navigate to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version
    Affected if Firmware version is lower than the affected threshold for your model (Cax80: 2.1.3.7, Lax20: 1.1.6.34, Mr60/Ms60: 1.1.6.124, Mr80/Ms80: 1.1.6.14, R6400: 1.0.1.78 or 1.0.4.126, R6700: 1.0.4.126)
  3. Verify readycloud feature status
    In the router web UI, look for ReadyCloud settings under Advanced > ReadyCloud or USB/Storage settings; check if the service is enabled or connected
    Affected if ReadyCloud functionality is enabled or the router shows a readycloud connection status
  4. Confirm libreadycloud.so presence
    Access router diagnostics or shell if available (via telnet/SSH or firmware extraction); search for the file libreadycloud.so in the /lib or /usr/lib directory structure
    Affected if The file libreadycloud.so exists on the device firmware

You are affected if your router model matches one of the affected models AND your firmware version is below the specified threshold AND the readycloud feature is enabled or the vulnerable library is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.1.78 / 1.0.4.126 / 1.1.6.14 or later
Fixed in 1.0.1.781.0.4.1261.1.6.14
Interim mitigation

Apply the vendor-supplied firmware patch from NETGEAR for this vulnerability. If no patch is available, disable the readycloud functionality and restrict network access to the router's management interface.

Recommended fix High confidence

NETGEAR firmware version 2.1.3.7 (Cax80), 1.1.6.34 (Lax20), 1.1.6.124 (Mr60/Ms60), 1.1.6.14 (Mr80/Ms80), or 1.0.4.126 (R6400/R6700) or later depending on model

  1. Identify your specific NETGEAR router model from the affected list (Cax80, Lax20, Mr60, Mr80, Ms60, Ms80, R6400, or R6700)
  2. Visit the NETGEAR support page at kb.netgear.com and navigate to your router model's downloads section
  3. Download the latest firmware version that matches or exceeds the fixed version for your model: 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.4.126+, R6700: 1.0.4.126+
  4. Access your router's web management interface (typically at 192.168.1.1)
  5. Navigate to the Administration > Firmware Update section
  6. Upload the downloaded firmware file and allow the router to complete the update process
  7. After reboot, verify the firmware version has been updated in the router status page
Caveat Firmware updates may reset router configuration to defaults; backup settings before upgrading and re-apply after update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cax80 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27647 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27647 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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