CVE intelligence and bounded remediation

CVE-2017-5521 — NETGEAR Multiple Devices Exposure of Sensitive Information Vulnerability

High CVSS 8.1 CISA KEV

An issue was discovered on NETGEAR R8500, R8300, R7000, R6400, R7300, R7100LG, R6300v2, WNDR3400v3, WNR3500Lv2, R6250, R6700, R6900, and R8000 devices. They are prone to password disclosure via simple crafted requests to the web management server. The bug is exploitable remotely if the remote management option is set, and can also be exploited given access to the router over LAN or WLAN. When trying to access the web panel, a user is asked to authenticate; if the authentication is canceled and password recovery is not enabled, the user is redirected to a page that exposes a password recovery token. If a user supplies the correct token to the page /passwordrecovered.cgi?id=TOKEN (and password recovery is not enabled), they will receive the admin password for the router. If password recovery is set the exploit will fail, as it will ask the user for the recovery questions that were previously set when enabling that feature. This is persistent (even after disabling the recovery option, the exploit will fail) because the router will ask for the security questions.

Severity
High
CVSS
8.1 (3.1)
Published
2017-01-17
CISA KEV
Known exploited
Ecosystem
operating-system

Affected products

  • netgear / r6200_firmware / 1.0.1.56_1.0.43
  • netgear / r6300_firmware / 1.0.2.78_1.0.58
  • netgear / vegn2610_firmware / 1.0.0.36
  • netgear / ac1450_firmware / 1.0.0.34_10.0.16
  • netgear / wnr1000v3_firmware / 1.0.2.68_60.0.93
  • netgear / wndr3700v3_firmware / 1.0.0.40_1.0.32

Showing 6 representative product identities from 13 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.