dbcve.org
Cbr40 FirmwareOperating system · Netgear

CVE-2023-36187

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-01
Fix available
A fix is available. Upgrade to 1.0.1.70 / 1.0.4.118 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
Buffer Overflow vulnerability in NETGEAR R6400v2 before version 1.0.4.118, allows remote unauthenticated attackers to execute arbitrary code via crafted URL to httpd.

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

Buffer overflow vulnerability in the httpd web server of NETGEAR R6400v2 routers allows remote unauthenticated attackers to execute arbitrary code by sending a specially crafted URL. The vulnerability affects firmware versions prior to 1.0.4.118.

MitigationUpgrade NETGEAR R6400v2 firmware to version 1.0.4.118 or later to remediate the vulnerability.

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
Cbr40 FirmwareOperating system
Affected:< 2.5.0.24
Lax20 FirmwareOperating system
Affected:< 1.1.6.34
Mk62 FirmwareOperating system
Affected:< 1.1.6.122
Mr60 FirmwareOperating system
Affected:< 1.1.6.122
Ms60 FirmwareOperating system
Affected:< 1.1.6.122
Rbw30 FirmwareOperating system
Affected:< 2.6.2.6
R6400 FirmwareOperating system
Affected:< 1.0.1.70
R6400v2 FirmwareOperating system
Affected:< 1.0.4.118

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 router model
    Log into the router web interface (typically at 192.168.1.1) and check the device information page, or look at the device label on the router itself
    Affected if The model is one of: Cbr40, Lax20, Mk62, Mr60, Ms60, Rbw30, R6400, or R6400v2
  2. Determine installed firmware version
    In the router web interface, go to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version
    Affected if The firmware version is below the threshold for your model: Cbr40 < 2.5.0.24, Lax20 < 1.1.6.34, Mk62/Mr60/Ms60 < 1.1.6.122, Rbw30 < 2.6.2.6, R6400 < 1.0.1.70, R6400v2 < 1.0.4.118
  3. Verify httpd web server is accessible
    Attempt to access the router login page from a remote client using the router's public IP or LAN IP (http://[router-ip])
    Affected if The router web interface responds to HTTP requests, indicating the vulnerable httpd service is running

Your router is affected if it matches one of the listed models AND its firmware version is below the specified threshold for that model, and the web interface is network-accessible.

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.70 / 1.0.4.118 / 1.1.6.34 or later
Fixed in 1.0.1.701.0.4.1181.1.6.34
Interim mitigation

Upgrade NETGEAR R6400v2 firmware to version 1.0.4.118 or later to remediate the vulnerability.

Recommended fix High confidence

R6400v2: 1.0.4.118 | R6400: 1.0.1.70 | Cbr40: 2.5.0.24 | Lax20: 1.1.6.34 | Mk62/Mr60/Ms60: 1.1.6.122 | Rbw30: 2.6.2.6

  1. 1. Identify your specific Netgear router model from the affected list (Cbr40, Lax20, Mk62, Mr60, Ms60, Rbw30, R6400, or R6400v2)
  2. 2. Access your router's web management interface by entering the router's IP address in a web browser
  3. 3. Navigate to the Administration or Firmware Update section (typically under Advanced > Administration > Firmware Update)
  4. 4. Check the current firmware version under the Router Status or Administration page
  5. 5. Download the appropriate fixed firmware version from the official NETGEAR support website (support.netgear.com) for your specific model
  6. 6. In the firmware update section, click Browse or Choose File and select the downloaded firmware file
  7. 7. Click Upload or Update to begin the firmware upgrade process
  8. 8. Wait for the upgrade to complete (do not power off the router during this process)
Caveat Firmware upgrades may reset router configuration to defaults; backup current settings before upgrading; ensure stable power during upgrade to avoid bricking

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

Fix this in Cbr40 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36187 — 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-2023-36187 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