dbcve.org
Rax30 FirmwareOperating system · Netgear

CVE-2023-40479

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.0.9.92 or later.
See remediation →
93/100
Remediation priority · Urgent
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 RAX30 UPnP Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR RAX30 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the UPnP service. 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-19704.

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

The NETGEAR RAX30 router contains a command injection vulnerability in its UPnP service. The flaw stems from insufficient validation of user-supplied input before it is passed to a system call, allowing an attacker to inject arbitrary commands. Since authentication is not required and the exploit executes with root privileges, an unauthenticated network-adjacent attacker can achieve full remote code execution on the affected device.

MitigationApply the NETGEAR firmware update when available; as a temporary compensating control, disable UPnP on the router and restrict management interface access to trusted networks.

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
Rax30 FirmwareOperating system
Affected:< 1.0.9.92

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
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 checks

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

  1. Identify the router model
    Access the router admin web interface (typically at 192.168.1.1) and look for the device model name in the status or settings page, or check the product label on the device itself
    Affected if Device model is Netgear RAX30 (other NETGEAR models are not affected by this specific CVE)
  2. Check the installed firmware version
    In the router admin interface, navigate to the firmware or version information section (usually under Advanced, Administration, or a Status page). Compare the displayed firmware version against 1.0.9.92
    Affected if Firmware version is less than 1.0.9.92 (for example, 1.0.9.90, 1.0.8.x, or earlier)
  3. Verify UPnP service status
    In the router admin interface, locate the UPnP settings (typically under Advanced, LAN Setup, or Port Forwarding/UPnP). Check whether UPnP is enabled or disabled
    Affected if UPnP is currently enabled on the device (the vulnerability only affects devices where UPnP is active)
  4. Confirm network accessibility to UPnP service
    Verify that the router is accessible on the local network and that UPnP is reachable. This may involve checking if UDP port 1900 (UPnP SSDP) responds or using a network scanner to confirm UPnP is exposed
    Affected if UPnP service is reachable from the network (an unauthenticated network-adjacent attacker requires this access to exploit the vulnerability)

The device is affected if it is a Netgear RAX30 router running firmware version prior to 1.0.9.92 AND the UPnP feature is enabled, allowing an unauthenticated network-adjacent attacker to achieve remote code execution.

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.9.92 or later
Fixed in 1.0.9.92
Interim mitigation

Apply the NETGEAR firmware update when available; as a temporary compensating control, disable UPnP on the router and restrict management interface access to trusted networks.

Recommended fix High confidence

1.0.9.92

  1. Identify the current firmware version of the NETGEAR RAX30 router
  2. Download the firmware version 1.0.9.92 or later from the official NETGEAR support site (kb.netgear.com)
  3. Access the router's web administration interface
  4. Navigate to the Firmware Update or Administration section
  5. Upload and apply the new firmware version
  6. Verify the firmware has been successfully updated to version 1.0.9.92 or later
Caveat Firmware updates carry inherent risk; ensure stable power during the update process and review release notes for any known issues

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

Fix this in Rax30 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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