dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Sep 2022.
Dgn2200 FirmwareOperating system · Netgear

CVE-2017-6077

CRITICAL · 9.8 CVSS v3.1 Published 2017-02-22
Fix available
A fix is available. Upgrade to after 10.0.0.50 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

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 · unedited
ping.cgi on NETGEAR DGN2200 devices with firmware through 10.0.0.50 allows remote authenticated users to execute arbitrary OS commands via shell metacharacters in the ping_IPAddr field of an HTTP POST 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 confidence

Command injection vulnerability in the ping.cgi script of NETGEAR DGN2200 routers (firmware 10.0.0.50 and earlier). The ping_IPAddr parameter in HTTP POST requests is not properly sanitized, allowing authenticated attackers to inject arbitrary OS commands via shell metacharacters.

MitigationUpdate router firmware to a patched version if available; otherwise restrict administrative access to trusted networks only and disable remote web management to reduce attack surface.

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
Dgn2200 FirmwareOperating system
Affected:<= 10.0.0.50

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router web interface and check the device information page, or look at the physical device label to confirm it is a NETGEAR DGN2200 model
    Affected if The device is not a NETGEAR DGN2200 router
  2. Determine the firmware version
    Log into the router web interface and navigate to the Administration or Router Status section to find the firmware version number
    Affected if The firmware version is 10.0.0.50 or lower
  3. Verify remote web management is accessible
    Attempt to access the router web interface from an external network location using the router's public IP address on port 80 or 443
    Affected if The web interface is accessible from outside the local network
  4. Confirm ping.cgi endpoint exists
    Check if the /ping.cgi endpoint responds by sending a test request to the router web interface
    Affected if The ping.cgi script is accessible and responds to requests
  5. Check authentication status
    Attempt to access the router web interface without credentials or check if default credentials are still in use
    Affected if The router web interface is accessible without authentication or uses default credentials

A user is affected if they have a NETGEAR DGN2200 router running firmware version 10.0.0.50 or lower with the web interface accessible either locally or remotely.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 10.0.0.50
Interim mitigation

Update router firmware to a patched version if available; otherwise restrict administrative access to trusted networks only and disable remote web management to reduce attack surface.

Recommended fix Moderate confidence

NETGEAR DGN2200 firmware version later than 10.0.0.50 (check NETGEAR support for latest available version)

  1. 1. Log in to the NETGEAR DGN2200 router web interface (typically at 192.168.1.1)
  2. 2. Navigate to the Administration or Router Upgrade section
  3. 3. Check the current firmware version under Router Info or similar
  4. 4. Visit the official NETGEAR support website and download the latest available firmware for the DGN2200 model
  5. 5. Upload the firmware file and wait for the device to reboot
  6. 6. After reboot, verify the new firmware version is installed
  7. 7. Confirm the ping functionality still works correctly
Caveat Firmware updates on older routers may reset configuration to defaults; back up current settings before upgrading if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dgn2200 Firmware Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6077 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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