NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DirtyWilly
Aug 20, 2021Star
R8500 Latest Firmware Version V1.0.2.154 Broke DNS!
Hello, the latest firmware version V1.0.2.154 for the R8500 router appears to have broken DNS! I have to refresh pages multiple times to get them to load. Attached is the most common error. DNS_PR...
JFII
Mar 27, 2022Guide
Allowing the router to dynamically retrieve the IP and DSN seems not to have the issue. When I was having the issue I was manually entering the IP and DNS it wasn't until I limited the DNS to 1 entry did the issue go away (and of course allowing them to be retrieved by the ISP)
I also reboot the device every week or so. Which bring up my the issue of using the device as a media server. When rebooting the R8500 does not remount the USB chip I have plugged into it. I have to physically remove the chip and plug it back it for it to work.
CogX
Mar 27, 2022Aspirant
So, count me as one who starting having the DNS "probe" errors as soon as I had installed firmware R8500-V1.0.2.154 last summer now. After a few days, once I realized it wasn't just me, I downgraded back to R8500-V1.0.2.144 and been there since.
However, it turns out, I do actually get those DNS errors sometimes even with .144, but it's temporary, it shows that error in Chrome for a second or two and then the page I'm trying to get to then does load. With .154, it wasn't re-loading and it was also happening in Firefox, not just Chrome.
Now, I do use a different DNS server than my ISP, and I did have both a primary and secondary set, but I just went in and took out the secondary. We'll see if get that DNS probe error again at some point with .144.
I guess the question for everyone fighting this Netgear bug, does everyone have manual DNS settings?
- CogXMar 27, 2022Aspirant
Well, that didn't take long, still got the brief DNS probe error screen in Chrome, on one of the usual websites where it happens.
- JFIIApr 10, 2022Guide
new firmware .158 released
- FURRYe38Apr 10, 2022Guru - Experienced User
Was mentioned already.
- CogXApr 10, 2022Aspirant
I don't really want to try .158, because I doubt it fixes this DNS bug, but more than that, CISA has listed three more security vulnerabilities that aren't yet fixed:
r8500_firmware NETGEAR R8500 1.0.2.158 devices allow remote authenticated users to execute arbitrary commands (such as telnetd) via shell metacharacters in the sysNewPasswd and sysConfirmPasswd parameters to password.cgi.
2022-03-26 9
CVE-2022-27945
netgear -- r8500_firmware NETGEAR R8500 1.0.2.158 devices allow remote authenticated users to execute arbitrary commands (such as telnetd) via shell metacharacters in the sysNewPasswd and sysConfirmPasswd parameters to admin_account.cgi.
2022-03-26 9
CVE-2022-27946
netgear -- r8500_firmware NETGEAR R8500 1.0.2.158 devices allow remote authenticated users to execute arbitrary commands (such as telnetd) via shell metacharacters in the ipv6_fix.cgi ipv6_wan_ipaddr, ipv6_lan_ipaddr, ipv6_wan_length, or ipv6_lan_length parameter.
2022-03-26 9
CVE-2022-27947
- webleeApr 11, 2022Guide
Well thanks for this post. It just about settles it for me. I need a newer, more secure router.
I have suspected the router was being accessed and updated/reconfigured but I dont get anything but DHCP activity in the logs which in itself is an indicator.
I have thought about placing a pfsense or sophos between the router and cable modem but thats just dressing up a pig IMO.
shopping I will go....