Rax30 FirmwareOperating system · Netgear

CVE-2023-1327

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-14
Fix available
A fix is available. Upgrade to 1.0.6.74 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 RAX30 (AX2400), prior to version 1.0.6.74, was affected by an authentication bypass vulnerability, allowing an unauthenticated attacker to gain administrative access to the device's web management interface by resetting the admin password.

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 (AX2400) router contains an authentication bypass vulnerability in versions prior to 1.0.6.74. An unauthenticated attacker can reset the admin password through the web management interface, gaining full administrative access without any credentials.

MitigationUpdate the Netgear RAX30 firmware to version 1.0.6.74 or later. If immediate patching is not possible, restrict external access to the device's web management interface using network segmentation or firewall rules.

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.6.74

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. Access the router web management interface
    Open a web browser and navigate to the Netgear RAX30 default gateway (typically http://192.168.1.1 or http://routerlogin.net). Look for the firmware version displayed on the login page or in the router status/dashboard area.
    Affected if The firmware version shown is below 1.0.6.74 (for example, 1.0.6.73 or earlier)
  2. Check firmware version in Administration settings
    If logged in, navigate to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version number.
    Affected if The installed firmware version is less than 1.0.6.74
  3. Cross-reference with Netgear support resources
    Visit the official Netgear support page for the RAX30 model and compare the installed version against the version history to confirm whether the fix (1.0.6.74) has been applied.
    Affected if The firmware version installed on the device is earlier than the patched version 1.0.6.74

The device is affected if the Netgear RAX30 is running any firmware version prior to 1.0.6.74, as this allows an unauthenticated attacker to reset the admin password through the web interface.

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.6.74 or later
Fixed in 1.0.6.74
Interim mitigation

Update the Netgear RAX30 firmware to version 1.0.6.74 or later. If immediate patching is not possible, restrict external access to the device's web management interface using network segmentation or firewall rules.

Recommended fix High confidence

1.0.6.74

  1. 1. Visit the official NETGEAR support website and navigate to the RAX30 product page
  2. 2. Locate the firmware download section
  3. 3. Download firmware version 1.0.6.74 or later
  4. 4. Access the router's web management interface at http://routerlogin.net or http://192.168.1.1
  5. 5. Navigate to the Administration > Firmware Update section
  6. 6. Click 'Check for Updates' or manually upload the downloaded firmware file
  7. 7. Wait for the firmware upload and installation to complete - do not power off the router
  8. 8. After reboot, verify the router is running version 1.0.6.74 or later in the Administration section

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1327 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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