dbcve.org
Rax30 FirmwareOperating system · Netgear

CVE-2023-34284

MEDIUM · 6.3 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.0.10.94 or later.
See remediation →
68/100
Remediation priority · Elevated
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 Use of Hard-coded Credentials Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of NETGEAR RAX30 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the system configuration. The system contains a hardcoded user account which can be used to access the CLI service as a low-privileged user. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-19660.

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 hardcoded user account in its system configuration that can be used to access the CLI service. An attacker with network adjacency to the device can leverage these hardcoded credentials to bypass authentication and gain low-privileged CLI access.

MitigationApply available firmware updates from NETGEAR. If no update is available, restrict network access to the router's management interface and consider disabling remote administration to reduce attack surface.

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

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 device model
    Access the router web interface at the default gateway IP (usually 192.168.1.1) and check the device information page, or run 'cat /proc/cpuinfo' or 'nvram get model' via CLI if accessible
    Affected if The device is not a NETGEAR RAX30 router
  2. Check the installed firmware version
    In the router web interface, go to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version. Alternatively, run 'nvram get firmware_version' via CLI if accessible
    Affected if The firmware version is lower than 1.0.10.94 (e.g., 1.0.10.93 or earlier)
  3. Locate the system configuration file
    Access the router configuration file via backup functionality (typically from Administration > Backup Settings in the web interface) or via CLI by examining /etc/config or /nvram configuration files
    Affected if A hardcoded user account exists in the configuration that is not a user-created account
  4. Verify CLI service accessibility
    Check if the CLI service is listening on the router by scanning common CLI ports (23/telnet, 22/ssh) or attempting a connection. In the web interface, check if 'Router Shell' or CLI access features are enabled under Advanced > Administration
    Affected if CLI service (telnet or SSH) is enabled and accessible on the device

The device is affected if it is a NETGEAR RAX30 router running firmware version below 1.0.10.94 with the hardcoded credentials present in the configuration and CLI service 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 available firmware updates from NETGEAR. If no update is available, restrict network access to the router's management interface and consider disabling remote administration to reduce attack surface.

Recommended fix High confidence

Rax30 Firmware version 1.0.10.94 or later

  1. 1. Download the fixed firmware version 1.0.10.94 or later from the official NETGEAR support website (kb.netgear.com) for the RAX30 router
  2. 2. Connect to the RAX30 router's web interface by entering the router's IP address in a web browser
  3. 3. Log in to the router admin panel with valid administrator credentials
  4. 4. Navigate to the 'Advanced' or 'Administration' section of the router settings
  5. 5. Select 'Firmware Update' or 'Router Update' option
  6. 6. 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 router to complete the upgrade and reboot automatically - do not power off the router during this process
Caveat Firmware upgrades may reset some custom configurations; reconfigure any personalized settings after upgrading

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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