dbcve.org
R8500 FirmwareOperating system · Netgear

CVE-2024-50994

MEDIUM · 5.7 CVSS v3.1 Published 2024-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 R8500 v1.0.2.160 was discovered to contain multiple stack overflow vulnerabilities in the component ipv6_fix.cgi via the ipv6_wan_ipaddr, ipv6_lan_ipaddr, ipv6_wan_length, and ipv6_lan_length parameters. These vulnerabilities allow attackers to cause a Denial of Service (DoS) via a crafted POST request.

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 R8500 router firmware v1.0.2.160 contains multiple stack overflow vulnerabilities in the ipv6_fix.cgi web component. Attackers can send specially crafted POST requests with excessively long values in the ipv6_wan_ipaddr, ipv6_lan_ipaddr, ipv6_wan_length, and ipv6_lan_length parameters, causing stack memory corruption that leads to device crash and Denial of Service.

MitigationApply the vendor-provided firmware patch when available. As an interim measure, disable remote web interface administration or restrict access to trusted IP addresses only 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
R8500 FirmwareOperating system
Affected:= 1.0.2.160

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify router model
    Access the router web interface or check the device label to confirm the model is Netgear R8500
    Affected if Router is not a Netgear R8500 model - this vulnerability only affects that specific model
  2. Check firmware version
    Log into the router web interface and navigate to Administration > Firmware Update or check the firmware version displayed in the status/dashboard page. Alternatively, check the version string in the firmware file or via SNMP if available
    Affected if Firmware version is not exactly 1.0.2.160 - only version 1.0.2.160 is listed as affected
  3. Verify ipv6_fix.cgi is accessible
    Attempt to access https://<router_ip>/ipv6_fix.cgi or check if the web server responds to that endpoint. This CGI handles IPv6 configuration in the router
    Affected if The ipv6_fix.cgi endpoint does not exist or is not accessible on the device
  4. Check if remote web interface administration is enabled
    In the router web interface, go to Advanced > Administration > Remote Management and check if remote management is enabled. Alternatively, test if the web interface is accessible from a different network IP
    Affected if Remote web administration is enabled - this allows external attackers to reach the vulnerable CGI component

You are affected if you have a Netgear R8500 router running firmware version 1.0.2.160 with the ipv6_fix.cgi component accessible, especially if remote web administration is 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided firmware patch when available. As an interim measure, disable remote web interface administration or restrict access to trusted IP addresses only to reduce attack surface.

Recommended fix Low confidence

Any firmware version newer than 1.0.2.160 that addresses the ipv6_fix.cgi stack overflow vulnerabilities (check Netgear release notes)

  1. 1. Visit the official Netgear support website at www.netgear.com/support/
  2. 2. Enter R8500 in the product search or browse to the R8500 product support page
  3. 3. Navigate to the Downloads/Firmware section
  4. 4. Check for any firmware versions newer than 1.0.2.160
  5. 5. Download the latest stable firmware version available
  6. 6. Access the router web interface at http://routerlogin.net or http://192.168.1.1
  7. 7. Navigate to Administration > Firmware Update or similar section
  8. 8. Upload and install the newer firmware version
Caveat Review Netgear release notes for the update - some firmware updates may reset configuration to defaults or have compatibility implications

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

Fix this in R8500 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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