CVE-2024-35518
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 EX6120 v1.0.0.68 is vulnerable to Command Injection in genie_fix2.cgi via the wan_dns1_pri parameter.
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 EX6120 router firmware v1.0.0.68 contains a command injection vulnerability in the genie_fix2.cgi web script. The wan_dns1_pri parameter, intended for primary DNS configuration, is not properly sanitized before being passed to system shell commands, allowing an authenticated attacker to inject arbitrary shell commands.
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.0.68CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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.
-
Check the router firmware versionLog into the router web management interface (typically at 192.168.1.1) and navigate to Administration > Firmware Update or Router Status page to view the current firmware version. Alternatively, check the label on the router device itself for the firmware version printed there.Affected if The firmware version is 1.0.0.68 or lower.
-
Verify the genie_fix2.cgi script existsAttempt to access the CGI script via HTTP/HTTPS by navigating to http://[router-ip]/genie_fix2.cgi or https://[router-ip]/genie_fix2.cgi in a web browser. A 404 error indicates the script may not be present, while a page load (even with errors) suggests it exists.Affected if The script loads or responds (not returning a 404), indicating the vulnerable endpoint is present on the device.
-
Confirm the web management interface is network-accessibleFrom a system on the same network, attempt to reach the router login page at http://192.168.1.1 or the router's configured IP address using a web browser or curl command: curl -I http://[router-ip]/Affected if The router web interface is reachable from network segments beyond the local LAN, increasing exposure to authenticated attackers.
-
Determine if default or weak administrative credentials are in useAttempt to log into the router web interface with default Netgear credentials (commonly admin/password or admin/1234) or check if the password has been changed from defaults.Affected if Default credentials are still active, making authentication-based exploitation feasible for remote attackers.
You are affected if your Netgear EX6120 runs firmware version 1.0.0.68 or lower, the genie_fix2.cgi script is present, and the web management interface is accessible to untrusted networks with valid (or default) admin credentials.
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.
From vendor dataRestrict administrative access to trusted networks only. Apply any available firmware update from Netgear. If no patch exists, consider network segmentation to limit exposure of the router's web management interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35518 — 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-2024-35518 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