CVE-2023-51634
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 · uneditedNETGEAR RAX30 Improper Certificate Validation Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to compromise the integrity of downloaded information on affected installations of NETGEAR RAX30 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the downloading of files via HTTPS. The issue results from the lack of proper validation of the certificate presented by the server. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-19589.
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 confidenceThe NETGEAR RAX30 router fails to validate SSL/TLS certificates when downloading files over HTTPS, allowing a network-adjacent attacker to perform a man-in-the-middle attack. By presenting a malicious certificate, the attacker can inject arbitrary content into downloads. When chained with other vulnerabilities, this enables unauthenticated remote code execution in the root context.
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< 1.0.12.100_hotfixCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router model and firmware versionLog into the router web interface (typically at 192.168.1.1) and navigate to Administration > Firmware Update or check the status page. Alternatively, use the NETGEAR Nighthawk app or check the device label.Affected if The device is a NETGEAR RAX30 and the firmware version is below 1.0.12.100_hotfix
-
Determine if automatic HTTPS downloads are enabledCheck router settings under Advanced > Administration > Remote Management, or look for any settings related to automatic firmware updates, app downloads, or network-assisted downloads that fetch files over HTTPS.Affected if Any feature that automatically downloads files from HTTPS sources is enabled on the router
-
Assess network exposureReview whether the router management interface is accessible from the WAN/internet side, or if the router is connected to untrusted networks (public WiFi, bridged networks with untrusted devices).Affected if The router management interface is exposed to the internet or the router operates on untrusted network segments where an attacker could perform MITM attacks
-
Verify SSL certificate validation is occurringFor any manual HTTPS downloads initiated from behind the router, capture network traffic using a packet sniffer on the LAN and inspect whether the router validates the server certificate properly. This is difficult to test directly but can be inferred from firmware version.Affected if The firmware version is vulnerable and HTTPS download features are in use
You are affected if you own a NETGEAR RAX30 router running firmware versions prior to 1.0.12.100_hotfix and use any feature that downloads files over HTTPS from the router.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.12.100_hotfix
Apply the NETGEAR firmware update when available. Until then, avoid using the router on untrusted networks and disable any features that automatically download files over HTTPS from unverified sources.
RAX30 Firmware version 1.0.12.100_hotfix
- 1. Download the firmware version 1.0.12.100_hotfix (or later) from the official NETGEAR support site (kb.netgear.com) for the RAX30 router model.
- 2. Access the NETGEAR RAX30 router web interface by navigating to the router's IP address (typically 192.168.1.1) in a web browser.
- 3. Log in to the router administration panel with administrator credentials.
- 4. Navigate to the Advanced tab, then select Administration > Firmware Update.
- 5. Click the 'Check for Updates' button to ensure you have the latest available version, or select the manual update option.
- 6. Upload the downloaded firmware file (1.0.12.100_hotfix) and initiate the update process.
- 7. Wait for the firmware upload to complete and the router to reboot. Do not power off the router during this process.
- 8. After the router restarts, log back into the web interface and verify the firmware version has been updated to 1.0.12.100_hotfix or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51634 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-51634 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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