CVE-2023-27357
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 GetInfo Missing Authentication Information Disclosure Vulnerability. This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of NETGEAR RAX30 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of SOAP requests. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to disclose sensitive information, leading to further compromise. Was ZDI-CAN-19608.
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 has an unauthenticated SOAP endpoint that exposes sensitive information. Attackers on the adjacent network can send SOAP requests to this endpoint without any credentials and retrieve sensitive configuration data, device credentials, or other confidential details that can facilitate further attacks.
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.10.94CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the router modelCheck the device label or login to the router admin interface to confirm the model is NETGEAR RAX30Affected if The device is a NETGEAR RAX30 router and the firmware version is below 1.0.10.94
-
Check the installed firmware versionLog into the router admin panel and navigate to the firmware version information page, typically under Administration > Firmware Update or a similar sectionAffected if The displayed firmware version is lower than 1.0.10.94
-
Determine if the SOAP service is accessibleFrom a device on the same network as the router, attempt to access the SOAP endpoint by sending an HTTP request to the router's IP address on common HTTP ports (80/443) and observe if a SOAP or UPnP service respondsAffected if The router responds to HTTP requests on the management interface without requiring authentication and exposes a SOAP or UPnP service
-
Verify network exposure of management interfaceCheck the router's firewall or access control settings to determine if the management interface (HTTP/HTTPS ports) is accessible from the WAN side or from adjacent networks beyond your trusted local networkAffected if The router's management interface (HTTP/HTTPS) is reachable from network segments outside the trusted local network, enabling adjacent network attackers to reach the SOAP endpoint
If the device is a NETGEAR RAX30 running firmware version lower than 1.0.10.94 and the SOAP management interface is accessible from adjacent networks, the environment is affected by this vulnerability.
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.10.94
Apply the vendor-supplied firmware update from NETGEAR when available. Until then, restrict network access to the router's management interfaces and disable WAN-side management if possible.
Rax30 Firmware version 1.0.10.94 or later
- Access the router's web interface by navigating to routerlogin.net or 192.168.1.1 in a web browser
- Log in with the router's administrator credentials
- Navigate to the Administration or Settings section
- Look for a Firmware Update or Router Update option
- Check for available updates and download version 1.0.10.94 or later
- Follow the on-screen prompts to install the firmware update
- Wait for the router to reboot and verify the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27357 — 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-27357 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