dbcve.org
Mr60 FirmwareOperating system · Netgear

CVE-2022-48322

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-13
Fix available
A fix is available. Upgrade to 1.1.7.132 / 1.3.3.154 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
NETGEAR Nighthawk WiFi Mesh systems and routers are affected by a stack-based buffer overflow vulnerability. This affects MR60 before 1.1.7.132, MS60 before 1.1.7.132, R6900P before 1.3.3.154, R7000P before 1.3.3.154, R7960P before 1.4.4.94, and R8000P before 1.4.4.94.

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

NETGEAR Nighthawk routers and mesh systems contain a stack-based buffer overflow vulnerability that could allow remote attackers to execute arbitrary code due to improper bounds checking. The vulnerability affects multiple popular router models (MR60, MS60, R6900P, R7000P, R7960P, R8000P) running firmware versions prior to the patched releases.

MitigationApply vendor-supplied firmware updates (MR60/MS60 to 1.1.7.132 or later; R6900P/R7000P to 1.3.3.154 or later; R7960P/R8000P to 1.4.4.94 or later). If updates are unavailable, restrict administrative interfaces to trusted networks and monitor for indicators of compromise.

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
Mr60 FirmwareOperating system
Affected:< 1.1.7.132
Ms60 FirmwareOperating system
Affected:< 1.1.7.132
R6900p FirmwareOperating system
Affected:< 1.3.3.154
R7000p FirmwareOperating system
Affected:< 1.3.3.154
R7960p FirmwareOperating system
Affected:< 1.4.4.94
R8000p FirmwareOperating system
Affected:< 1.4.4.94

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

CVSS:3.1/AV:N/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 checks

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

  1. Identify the router model
    Locate the model number on the device label or log into the router admin web interface (typically at 192.168.1.1) and check the status or device info page
    Affected if The model is one of: MR60, MS60, R6900P, R7000P, R7960P, R8000P
  2. Find the installed firmware version
    In the router admin web interface, navigate to Advanced > Administration > Router Update or Check for New Version. The current firmware version is displayed on the status or dashboard page
    Affected if Unable to determine the firmware version or version displays as unknown
  3. Compare firmware version against affected ranges
    Compare your installed firmware version to the vulnerable thresholds: MR60/MS60 versions below 1.1.7.132; R6900P/R7000P versions below 1.3.3.154; R7960P/R8000P versions below 1.4.4.94
    Affected if Your installed firmware version falls below the corresponding threshold for your model
  4. Check remote administration settings
    In the router admin interface, go to Advanced > Administration > Remote Management. Verify if Remote Management is enabled and which IP addresses are allowed
    Affected if Remote Management is enabled and accessible from any IP address (0.0.0.0) or from untrusted networks

You are affected if your router model matches one of the six listed models AND your current firmware version is below the patch threshold for that model AND the admin interface is exposed to remote attackers.

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.1.7.132 / 1.3.3.154 / 1.4.4.94 or later
Fixed in 1.1.7.1321.3.3.1541.4.4.94
Interim mitigation

Apply vendor-supplied firmware updates (MR60/MS60 to 1.1.7.132 or later; R6900P/R7000P to 1.3.3.154 or later; R7960P/R8000P to 1.4.4.94 or later). If updates are unavailable, restrict administrative interfaces to trusted networks and monitor for indicators of compromise.

Recommended fix Moderate confidence

MR60/MS60: Firmware 1.1.7.132 | R6900P/R7000P: Firmware 1.3.3.154 | R7960P/R8000P: Firmware 1.4.4.94

  1. Access the NETGEAR router web interface by navigating to routerlogin.net or 192.168.1.1 in a web browser
  2. Log in with the router administrator credentials
  3. Navigate to the Administration or Advanced settings section
  4. Locate the Firmware Update or Router Update option
  5. Check for available updates - the router should show version 1.1.7.132 for MR60/MS60, 1.3.3.154 for R6900P/R7000P, or 1.4.4.94 for R7960P/R8000P as the fixed release
  6. If the update is not automatically detected, download the firmware from the official NETGEAR support website (kb.netgear.com) for your specific model
  7. Upload and apply the firmware file through the web interface
  8. Wait for the router to reboot and complete the update process
Caveat Firmware updates may temporarily interrupt network connectivity; ensure stable power during the update process

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

Fix this in Mr60 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-48322 — 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-48322 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