5 ms·
OP here, Yes, I agree, we (modemly) could do better 1. Show the vulnerability status (patched / open) 2. Show affected firmware versions 3. Display manufacture
by ndata 5y ago
OP here, Yes, I agree, we (modemly) could do better
1. Show the vulnerability status (patched / open)
2. Show affected firmware versions
3. Display manufacturer's last patch release date
Though lots of the dataset is clean, still we do lots of parsing and regexing to extract insights out of a massive haystack. The intention of this tool is for everyone to realize and keep their firmware updated
And No, we don't sell any services. The security reminder emails are free
- ndata 5y agoOP here. To clarify. The affected firmware versions are always available in the detailed description text. Its just that we couldn't show them in the header due to parsing failures in few cases
- chasil 5y agoA few questions. I am guessing that very few of these can be exploited on the side that faces the public internet. True? What percentage require access to the router via administrative login on the private network? How many would need nothing but a hostile .exe on the private network? How many could achieve an exploit with nothing but hostile JavaScript on the private network? Will changing the private network away from 192.168.* to something on 10.* protect a vulnerable router from some of these exploits? What else can be done to protect a vulnerable router?