CVE-2024-51005
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 R8500 v1.0.2.160 was discovered to contain a command injection vulnerability in the share_name parameter at usb_remote_smb_conf.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 confidenceA command injection vulnerability exists in Netgear R8500 router firmware v1.0.2.160. The flaw is located in the share_name parameter of the usb_remote_smb_conf.cgi script, allowing remote attackers to inject and execute arbitrary OS commands by sending specially crafted requests.
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.2.160CVSS 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.
-
Identify the router modelCheck the device label or access the admin interface to confirm the model is Netgear R8500Affected if The device is not a Netgear R8500 router - this vulnerability only affects that specific model
-
Check the installed firmware versionAccess the router admin web interface (typically at 192.168.1.1), navigate to Administration > Firmware Update or Advanced > Administration > Router Update, and note the firmware version displayedAffected if The firmware version is 1.0.2.160 - this is the only affected version listed for this CVE
-
Verify the vulnerable CGI script existsAttempt to access the URI /usb_remote_smb_conf.cgi on the router (e.g., http://192.168.1.1/usb_remote_smb_conf.cgi) using a web browser or curl commandAffected if The script is accessible and returns a response - this indicates the SMB remote sharing interface is present on the device
-
Check if USB remote SMB sharing feature is enabledIn the router admin interface, navigate to Advanced > USB Storage > ReadySHARE, or check for USB-related settings where remote SMB access can be enabled. Look for options related to 'Remote Access' or 'Remote SMB' sharingAffected if USB remote SMB sharing is enabled - this is the condition required for the command injection to be exploitable
You are affected if you have a Netgear R8500 router running firmware version 1.0.2.160 with the USB remote SMB sharing feature enabled and the usb_remote_smb_conf.cgi script accessible on your network.
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 the latest Netgear firmware update for the R8500 if available, or disable the USB remote SMB sharing feature if not needed, and restrict network access to the device management interface.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51005 — 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-51005 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