CVE-2024-35520
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 R7000 1.0.11.136 is vulnerable to Command Injection in RMT_invite.cgi via device_name2 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 confidenceCommand injection vulnerability in Netgear R7000 router firmware 1.0.11.136 allows remote attackers to execute arbitrary OS commands via the device_name2 parameter in RMT_invite.cgi. The lack of proper input sanitization on this parameter enables injection of shell metacharacters into backend system calls.
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.11.136CVSS 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.
-
Identify router modelAccess the router admin web interface (typically at 192.168.1.1) and navigate to the status or advanced settings page to confirm the device model is Netgear R7000. Alternatively, check the physical device label.Affected if The device is not a Netgear R7000 (different models are not affected by this specific CVE)
-
Check firmware versionIn the router admin interface, go to Advanced > Administration > Router Update or similar section and note the displayed firmware version number.Affected if The installed firmware version is exactly 1.0.11.136 (other versions are not affected by this specific CVE)
-
Verify remote management statusIn the router admin interface, look for 'Remote Management' or settings containing 'RMT' under Advanced > Administration > Remote Management. Check if it is enabled.Affected if Remote management is enabled, allowing external access to the RMT_invite.cgi endpoint
-
Confirm web interface exposureAttempt to access the router's web interface from an external network (outside your local network) or check if port forwarding/port 80/443 is exposed to WAN.Affected if The router admin web interface is accessible from untrusted networks (WAN side)
You are affected if your Netgear R7000 router is running firmware version 1.0.11.136 AND the RMT_invite.cgi endpoint (via remote management or exposed web interface) is accessible from an attacker's network location.
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-supplied firmware patch when available; until then, restrict administrative access to the router's web interface to trusted networks only and disable remote management if feasible.
- Consultation2.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 $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35520 — 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-35520 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