CVE-2016-6277
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 R6250 before 1.0.4.6.Beta, R6400 before 1.0.1.18.Beta, R6700 before 1.0.1.14.Beta, R6900, R7000 before 1.0.7.6.Beta, R7100LG before 1.0.0.28.Beta, R7300DST before 1.0.0.46.Beta, R7900 before 1.0.1.8.Beta, R8000 before 1.0.3.26.Beta, D6220, D6400, D7000, and possibly other routers allow remote attackers to execute arbitrary commands via shell metacharacters in the path info to cgi-bin/.
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 multiple NETGEAR router models allows remote attackers to execute arbitrary OS commands via shell metacharacters in the path info to the cgi-bin/ endpoint. The lack of input sanitization on the HTTP path parameter permits direct shell command injection.
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.22<= 1.0.0.56<= 1.0.4.6_10.1.12<= 1.0.1.18<= 1.0.1.14<= 1.0.1.14<= 1.0.7.2_1.1.93<= 1.0.0.28CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 modelLocate the model number on the router device label or access the web admin interface (typically at 192.168.1.1) and check the status or administration page for the model nameAffected if The model is one of: D6220, D6400, R6250, R6400, R6700, R6900, R7000, or R7100lg
-
Locate firmware versionAccess the router web admin interface and navigate to the Administration or Firmware Upgrade section to find the current firmware version numberAffected if Unable to retrieve firmware version or version is unpatched
-
Compare firmware version against affected rangesCheck the installed firmware version against the vulnerable versions: D6220 <= 1.0.0.22, D6400 <= 1.0.0.56, R6250 <= 1.0.4.6_10.1.12, R6400 <= 1.0.1.18, R6700 <= 1.0.1.14, R6900 <= 1.0.1.14, R7000 <= 1.0.7.2_1.1.93, R7100lg <= 1.0.0.28Affected if The installed firmware version falls at or below the version listed for your model
-
Verify cgi-bin exposureConfirm that the router web interface (specifically the /cgi-bin/ path) is accessible from untrusted networks such as the internet, typically by testing remote access settings in the router admin panel or attempting outbound accessAffected if Remote web management is enabled and the cgi-bin interface is reachable from external networks
The environment is affected if the router model and firmware version match one of the vulnerable combinations and the web interface is accessible to untrusted networks.
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.
dbcve · scopedApply vendor-provided firmware updates for all affected router models. If firmware updates are unavailable, restrict router management interface access to trusted networks or disable remote WAN management.
R6250: 1.0.4.6.Beta or later | R6400: 1.0.1.18.Beta or later | R6700: 1.0.1.14.Beta or later | R7000: 1.0.7.6.Beta or later | R7100LG: 1.0.0.28.Beta or later | D6220: 1.0.0.22 or later | D6400: 1.0.0.56 or later
- 1. Identify your NETGEAR router model from the affected list (D6220, D6400, R6250, R6400, R6700, R6900, R7000, R7100LG)
- 2. Check your current firmware version by logging into the router web interface and navigating to Administration > Firmware Update or checking the router status page
- 3. Download the appropriate fixed firmware from the official NETGEAR support website (kb.netgear.com) for your specific model
- 4. In the router web interface, go to Advanced > Administration > Firmware Update
- 5. Click 'Upload' and select the downloaded firmware file
- 6. Wait for the firmware upload and installation to complete - do not power off the router during this process
- 7. After reboot, verify the new firmware version is installed and matches or exceeds the fixed version for your model
- 8. After upgrading, consider performing a factory reset and reconfiguring the router to ensure a clean state
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6277 — 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-2016-6277 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