# CVE-2017-6077: NETGEAR DGN2200 Remote Code Execution

> Authenticated attackers can execute arbitrary OS commands on NETGEAR DGN2200 routers via the ping interface.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 7 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-hjrc-qggq-2w49

## What is CVE-2017-6077?

CVE-2017-6077 is a critical command injection vulnerability in n/a, published on 22 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2017-6077?

It affects 1 product.


Products: Netgear Dgn2200 Firmware.

## How do I fix CVE-2017-6077?

No fix has been published for CVE-2017-6077 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 7 Sep 2022.

## Is CVE-2017-6077 being exploited?

Yes. Attackers have exploited CVE-2017-6077 in the wild since at least 7 Mar 2022.

Public exploit code:

- Netgear DGN2200v1/v2/v3/v4 - 'ping.cgi' Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-17373](https://insights.sbomify.com/CVE-2019-17373/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-5649](https://insights.sbomify.com/CVE-2016-5649/): Netgear DGN2200 and DGND3700 disclose the administrator password (critical 9.8)
- [CVE-2024-57046](https://insights.sbomify.com/CVE-2024-57046/): Auth bypass in n/a (high 8.8)
- [CVE-2017-18755](https://insights.sbomify.com/CVE-2017-18755/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-6366](https://insights.sbomify.com/CVE-2017-6366/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6077 and fix it if it is affected.

What it is: CVE-2017-6077 is a critical command injection vulnerability in n/a, published on 22 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-6077 in the wild since at least 7 Mar 2022.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6077/ (Markdown: https://insights.sbomify.com/CVE-2017-6077/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6077
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6077
- OSV: https://osv.dev/vulnerability/CVE-2017-6077

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6077/
Summaries are generated and may contain mistakes; the official description above is the record.