Threats / NETGEAR / CVE-2017-6077
CVE-2017-6077
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
NETGEAR Wireless Router DGN2200 vulnerability
NETGEAR DGN2200 wireless routers are vulnerable to remote code execution via OS command injection, allowing unauthenticated attackers to execute arbitrary commands with router privileges.
Verdict
Today item — known-exploited.
This vulnerability enables direct system compromise of affected routers. The high EPSS score and confirmed exploitation in the wild indicate active abuse. Attackers can gain full control to pivot into networks, intercept traffic, or deploy persistent malware.
CISA KEV Yes · 2022-03-074EPSS 0.68712 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-07).
Probability (EPSS)
EPSS 0.68712 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: NETGEAR, Wireless Router DGN2200. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1839 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify a DGN2200 router exposed to the internet and craft a malicious request exploiting the command injection flaw.
Business
Network perimeter is compromised; the router becomes an attacker-controlled asset inside the trusted boundary.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute system commands on the router to establish persistence, modify firewall rules, or enable remote access.
Business
Attacker gains sustained presence; legitimate security controls are bypassed or disabled.
3
Lateral reach — past segmentation narrative 3
Attacker
I intercept or redirect internal network traffic, capture credentials, or launch attacks against connected devices.
Business
Confidentiality and integrity of internal communications are violated; downstream systems face secondary compromise risk.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.