CVE-2019-20755 json
Certain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user.
published 6y ago modified 4mo ago also EUVD-2019-11294
- cvss
- 6.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Certain NETGEAR devices are affected by a stack-based buffer overflow by an authenticated user. This affects D6220 before 1.0.0.46, D6400 before 1.0.0.80, D7000v2 before 1.0.0.51, D8500 before 1.0.3.42, DGN2200v1 before 1.0.0.58, DGN2200B before 1.0.0.58, JNDR3000 before 1.0.0.24, RBW30 before 2.1.4.16, R6250 before 1.0.4.26, R6300v2 before 1.0.4.28, R6400 before 1.0.1.42, R6400v2 before 1.0.2.56, R6700 before 1.0.1.46, R6900 before 1.0.1.46, R7000 before 1.0.9.32, R6900P before 1.3.1.44, R7100LG before 1.0.0.46, R7300DST before 1.0.0.68, R7000P before 1.3.1.44, R7900 before 1.0.2.16, R8000P before 1.4.0.10, R7900P before 1.4.0.10, R8300 before 1.0.2.122, R8500 before 1.0.2.122, R8000 before 1.0.4.18, WNDR3400v3 before 1.0.1.22, WNDR4500v2 before 1.0.0.72, WNR3500Lv2 before 1.2.0.54, WN3100RP before 1.0.0.20, and WN2500RPv2 before 1.0.1.54.
Patch / fix
- netgear d6220_firmware 1.0.0.46
- netgear d6400_firmware 1.0.0.80
- netgear d7000_firmware 1.0.0.51
- netgear d8500_firmware 1.0.3.42
- netgear dgn2200_firmware 1.0.0.58
- netgear dgn2200b_firmware 1.0.0.58
- netgear jndr3000_firmware 1.0.0.24
- netgear rbw30_firmware 2.1.4.16
- netgear r6250_firmware 1.0.4.26
- netgear r6300_firmware 1.0.4.28
- netgear r6400_firmware 1.0.1.42, 1.0.2.56
- netgear r6700_firmware 1.0.1.46
- netgear r6900_firmware 1.0.1.46
- netgear r7000_firmware 1.0.9.32
- netgear r6900p_firmware 1.3.1.44
- netgear r7100lg_firmware 1.0.0.46
- netgear r7300dst_firmware 1.0.0.68
- netgear r7000p_firmware 1.3.1.44
- netgear r7900_firmware 1.0.2.16
- netgear r8000p_firmware 1.4.0.10
Is CVE-2019-20755 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 FencerExploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.8 | CVSS:3.0/AC:L/AV:A/A:H/C:H/I:H/PR:H/S:U/UI:N |
| NVD | 3.1 | 6.8 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.0 | 6.8 | CVSS:3.0/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.2 | AV:A/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
Sources
- CVE List CVE-2019-20755
- NVD CVE-2019-20755
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.