dbcve.org
Rax30 FirmwareOperating system · Netgear

CVE-2023-27368

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.0.10.94 or later.
See remediation →
93/100
Remediation priority · Urgent
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 soap_serverd Stack-based Buffer Overflow Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR RAX30 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the soap_serverd binary. When parsing SOAP message headers, the process does not properly validate the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-19839.

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

Stack-based buffer overflow in the soap_serverd binary when parsing SOAP message headers allows unauthenticated network-adjacent attackers to bypass authentication and execute arbitrary code on NETGEAR RAX30 routers due to improper length validation before copying user-supplied data to a fixed-size stack buffer.

MitigationApply NETGEAR firmware updates when available; meanwhile, restrict network access to the router's management interface using firewall rules or network segmentation to limit exposure to adjacent attackers.

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

CVSS:3.1/AV:A/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. Confirm device model is Netgear RAX30
    Access the router web interface or check the device label to verify the exact model number is RAX30
    Affected if The device is not a Netgear RAX30 router, this CVE does not apply
  2. Check installed firmware version
    Log into the router web interface and navigate to Administration > Firmware Update, or use the NETGEAR mobile app, to view the current firmware version
    Affected if The firmware version is 1.0.10.94 or higher, the vulnerability is patched; versions below 1.0.10.94 are affected
  3. Verify soap_serverd binary is present and running
    Access router via SSH if enabled and run: ps | grep soap_serverd, or check /proc/<pid>/cmdline for the soap_serverd process
    Affected if The soap_serverd process is running - this is the vulnerable component that exposes the SOAP interface
  4. Check network exposure to SOAP service
    From a network-adjacent host, attempt to reach the SOAP endpoint: curl -X POST http://<router_ip>/soap_serverd (port 80/443), or scan for open ports on the router that serve SOAP
    Affected if The SOAP service is accessible from an untrusted network segment, an adjacent attacker could exploit this flaw

A Netgear RAX30 router running firmware versions below 1.0.10.94 with the soap_serverd process exposed to network-adjacent attackers is affected by this vulnerability.

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 NETGEAR firmware updates when available; meanwhile, restrict network access to the router's management interface using firewall rules or network segmentation to limit exposure to adjacent attackers.

Recommended fix High confidence

Rax30 Firmware 1.0.10.94

  1. 1. Identify the current firmware version of the NETGEAR RAX30 router by accessing the web management interface and checking the router status or firmware version information.
  2. 2. Download the firmware version 1.0.10.94 or later from the official NETGEAR support website (kb.netgear.com) specific to the RAX30 model.
  3. 3. Access the router's web management interface and navigate to the Firmware Update or Administration section.
  4. 4. Upload the downloaded firmware file and allow the router to complete the update process. Do not power off the router during the update.
  5. 5. After the router restarts, verify the firmware has been updated successfully by checking the firmware version in the router's status page.

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

Fix this in Rax30 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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