Skip to content
Fencer Intel
medium 6.5

CVE-2020-17409 json

This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of NETGEAR R6120, R6080, R…

published 6y ago modified 4mo ago also EUVD-2020-9362

cvss
6.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

This vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of NETGEAR R6120, R6080, R6260, R6220, R6020, JNR3210, and WNR2020 routers with firmware 1.0.66. Authentication is not required to exploit this vulnerability. The specific flaw exists within the mini_httpd service, which listens on TCP port 80 by default. The issue results from incorrect string matching logic when accessing protected pages. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-10754.

Patch / fix

  • netgear r6020_firmware 1.0.0.44
  • netgear r6080_firmware 1.0.0.44
  • netgear r6120_firmware 1.0.0.70
  • netgear r6220_firmware 1.1.0.100
  • netgear r6230_firmware 1.1.0.100
  • netgear r6260_firmware 1.1.0.76
  • netgear r6330_firmware 1.1.0.76
  • netgear r6350_firmware 1.1.0.76
  • netgear r6850_firmware 1.1.0.76

Is CVE-2020-17409 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 6.5 CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 3.3 AV:A/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • NETGEAR Multiple Routers

Classification

Weakness
  • CWE-288 Authentication Bypass Using an Alternate Path or Channel

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.