NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Jetdrive
Mar 07, 2020Luminary
Netgear routers are at risk of getting hacked: What to do
Netgear this week has pushed out a passel of patches for its home networking gear, covering seven modem-router gateways, one range extender and 40-odd routers, including some Nighthawk models and Orb...
tomschmidt
Mar 07, 2020Virtuoso
NG can't even fix their SSL cert that expired last August, that gives me little confidence they have a fix for this, as no March 2020 updates are available on their site yet.
Jetdrive
Mar 07, 2020Luminary
From the Threatpost.com website three days ago:
Netgear is urging customers to visit its online support page and search by device model for the most recent firmware to update and patch their devices.
OK Netgear, where are you hiding the updates?
- CrimpOnMar 07, 2020Guru - Experienced User
I think the moderators will enjoy asking the "powers that be" what the h**l they were thinking to announce something that can so easily be shown to be false. Dustin_V
- JetdriveMar 07, 2020Luminary
The worst thing about this is when Netgear announced exactly what these vulnerabilities are and to which models, the hackers now know exactly what to do. They don't have to test and try different hacks -- Netgear has left us like sitting ducks just waiting to be hacked.
Netgear could you please post the firmware updates?
- tomschmidtMar 07, 2020Virtuoso
Here is the list for the Orbis: https://kb.netgear.com/000061762/Security-Advisory-for-Stored-Cross-Site-Scripting-on-Some-Routers-Gateways-and-WiFi-Systems-PSV-2018-0533
These vulnerabilities appear to all be reported in 2018! Why is it taking them 2 years to fix known vulnerabilities?
All security bulletins are at https://www.netgear.com/about/security/ and you can subscribe to them if desired. You can also enter your model in the search to see what vulnerabilities apply to your NG product. For RBR50 & RBS50 (RBK50, RBK53), it appears that versions prior to v2.3.5.30 are affected.