CVE-2024-52018
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 XR300 v1.0.3.78 was discovered to contain a command injection vulnerability in the system_name parameter at genie_dyn.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 · moderate confidenceOS command injection vulnerability in Netgear XR300 router firmware v1.0.3.78. The genie_dyn.cgi web interface fails to properly sanitize the system_name parameter, allowing attackers to inject and execute arbitrary operating system commands on the device.
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.3.78CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Netgear XR300Log into the router admin panel and check the device information page, or run 'grep model /proc/cpuinfo' via telnet/SSH if availableAffected if Device is not a Netgear XR300 router
-
Check installed firmware versionNavigate to Router Administration > Firmware Update or check the status/diagnostics page in the web interface; on the device, run 'cat /etc/version' or check 'nvram get firmware_version'Affected if Firmware version is 1.0.3.78 exactly
-
Verify genie_dyn.cgi endpoint existsAttempt to access http://router-ip/cgi-bin/genie_dyn.cgi?system_name=test via HTTP request and check for a valid response (even an error)Affected if The CGI endpoint responds, indicating it is present and potentially vulnerable
-
Confirm web management interface is enabledCheck router settings under Administration > Remote Management, or attempt to access the router's web interface from both LAN and WAN IP addressesAffected if The web management interface is accessible (either locally or remotely)
-
Check if remote management is enabledIn the router web UI, navigate to Advanced > Administration > Remote Management and verify if 'Enable Remote Management' or 'Allow external access' is checkedAffected if Remote management is enabled, making the vulnerability exploitable from the WAN
You are affected if you are running Netgear XR300 firmware version 1.0.3.78 with the web management interface enabled, particularly if remote management is turned on.
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 dataApply vendor firmware patch if available; otherwise restrict access to the router's web management interface to trusted networks or disable remote management.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52018 — 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-52018 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