dbcve.org
R8500 FirmwareOperating system · Netgear

CVE-2024-52019

HIGH · 8.0 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 →
82/100
Remediation priority · High
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 a command injection vulnerability in the wan_gateway parameter at genie_fix2.cgi. This vulnerability allows attackers to execute arbitrary OS commands via a crafted 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

A command injection vulnerability exists in the genie_fix2.cgi endpoint of the Netgear R8500 router firmware v1.0.2.160. The vulnerability stems from insufficient input validation of the wan_gateway parameter, allowing attackers to inject and execute arbitrary operating system commands by sending crafted requests to the affected CGI script.

MitigationApply the vendor-supplied firmware patch if available; otherwise, disable remote management interfaces or network-segment the device to limit exposure, as the CVSS 8 score indicates high risk of complete system compromise.

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

CVSS:3.1/AV:A/AC:L/PR:L/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. Identify the router model
    Check the device label or login to the router admin interface to confirm the model is Netgear R8500
    Affected if Device is not a Netgear R8500 router
  2. Check the installed firmware version
    Log into the router admin interface and navigate to Administration > Firmware Update or check the version displayed on the dashboard. Alternatively, check the version string in the web interface footer or system info page.
    Affected if Firmware version equals 1.0.2.160
  3. Determine if remote management is enabled
    Log into the router admin interface and navigate to Advanced > Remote Management. Check if the 'Enable Remote Management' or 'Allow remote management' checkbox is selected or if the remote management port is open on the WAN interface.
    Affected if Remote management is enabled and accessible from WAN
  4. Check if the genie_fix2.cgi endpoint is reachable
    From an external network (or using a tool like curl), attempt to access http://<wan-ip>/genie_fix2.cgi. If the device is accessible remotely, this endpoint will respond.
    Affected if The genie_fix2.cgi endpoint is accessible and the router is running firmware 1.0.2.160

You are affected if you have a Netgear R8500 router running firmware version 1.0.2.160 with remote management enabled, which exposes the vulnerable genie_fix2.cgi endpoint.

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-supplied firmware patch if available; otherwise, disable remote management interfaces or network-segment the device to limit exposure, as the CVSS 8 score indicates high risk of complete system compromise.

Recommended fix Moderate confidence

Netgear R8500 latest available firmware (check Netgear support for version newer than 1.0.2.160)

  1. 1. Visit the official Netgear support website at www.netgear.com and navigate to the R8500 product support page.
  2. 2. Download the latest available firmware version for the Netgear R8500 router.
  3. 3. Access the router's web management interface (typically at 192.168.1.1).
  4. 4. Navigate to the Administration > Firmware Update section.
  5. 5. Upload and install the downloaded firmware file.
  6. 6. After the router restarts, verify the new firmware version in the router administration panel.
  7. 7. As a temporary mitigation before patching, restrict access to the genie_fix2.cgi endpoint using router access controls or firewall rules.
Caveat Firmware updates on older router models may occasionally reset configuration to defaults; back up current settings before upgrading

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

Fix this in R8500 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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