dbcve.org
Rax30 FirmwareOperating system · Netgear

CVE-2023-27356

HIGH · 8.0 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.0.10.94 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
NETGEAR RAX30 logCtrl Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR RAX30 routers. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the logCtrl action. 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-19825.

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

Command injection vulnerability in NETGEAR RAX30 router's logCtrl action. The flaw lacks proper validation of user-supplied strings before passing them to a system call. Although authentication is required, it can be bypassed, enabling arbitrary code execution with root privileges.

MitigationApply the latest NETGEAR firmware update for RAX30. If unavailable, restrict administrative access to trusted networks or disable remote management.

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.10.94
Raxe300 FirmwareOperating system
Affected:< 1.0.10.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
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
    Locate the model number on the device label or check the admin web interface (usually at 192.168.1.1) for the model designation in the status or settings page
    Affected if The device is a NETGEAR RAX30 or RAXE300 router
  2. Check firmware version
    Log into the router admin interface, navigate to Administration > Firmware Update or Advanced > Administration > Router Update, and note the current firmware version displayed
    Affected if The installed firmware version is lower than 1.0.10.94 (for example, 1.0.10.92 or earlier)
  3. Verify logCtrl endpoint accessibility
    Attempt to access the logCtrl functionality via the router's web interface or check if the /logCtrl endpoint responds (typically under advanced settings or logging features)
    Affected if The logCtrl feature is present and accessible in the web interface
  4. Check remote management settings
    In the router admin interface, go to Advanced > Administration > Remote Management and verify whether remote access is enabled
    Affected if Remote management is enabled and the admin interface is accessible from the internet or an untrusted network

A user is affected if they have a RAX30 or RAXE300 router running firmware version below 1.0.10.94 with the logCtrl feature accessible, especially if remote management is enabled.

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.10.94 or later
Fixed in 1.0.10.94
Interim mitigation

Apply the latest NETGEAR firmware update for RAX30. If unavailable, restrict administrative access to trusted networks or disable remote management.

Recommended fix High confidence

Firmware version 1.0.10.94 or later for NETGEAR RAX30 and RAXE300 routers

  1. 1. Identify the exact router model (RAX30 or RAXE300) from the device label
  2. 2. Navigate to the official NETGEAR support page (support.netgear.com) and locate the firmware download section for your model
  3. 3. Download firmware version 1.0.10.94 or later for your specific router model
  4. 4. Access the router's web management interface by entering the router's IP address in a web browser
  5. 5. Log in with administrator credentials
  6. 6. Navigate to the Advanced tab > Administration > Firmware Update (or similar path depending on exact model UI)
  7. 7. Select the downloaded firmware file and initiate the update
  8. 8. Wait for the router to reboot and complete the update process

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

Fix this in Rax30 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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