If you’re in modem only mode, block HTTP traffic to 192.168.100.1 outbound from your firewall just to be sure.
Seems relatively low impact, but still pretty bad. Not surprising from VM given the quality of their firmware.
If you’re in modem only mode, block HTTP traffic to 192.168.100.1 outbound from your firewall just to be sure.
Seems relatively low impact, but still pretty bad. Not surprising from VM given the quality of their firmware.
I've been blocking traffic to RFC1918 ranges (all of them) that attempts to egress the WAN interface for just as long.
It's almost like I knew that eventually, someone was going to find a vulnerability in their web panel, and I wanted to make sure it wouldn't be exploitable.
Oh wait, I didn't know. It's just common sense.
What does it return in modem only mode? I've verified that <hubip>/snmpGet?oid=1.3.6.1.4.1.4115.1.20.1.1.1.7.1.3.1 on my Hub 3 returns:
> { > "1.3.6.1.4.1.4115.1.20.1.1.1.7.1.3.1":"$xxxxxxxx" [public IP address encoded in hexadecimal] > }
but I can't currently test it in modem only mode.
$ ssh -L 127.0.0.1:1234:192.168.100.1:80 root@router
$ curl 'http://127.0.0.1:1234/snmpGet?oid=1.3.6.1.4.1.4115.1.20.1.1.1.7.1.3.1'
{
"1.3.6.1.4.1.4115.1.20.1.1.1.7.1.3.1":"$00000000"
}
It does not appear to work in modem mode.{ "1.3.6.1.4.1.4115.1.20.1.1.1.7.1.3.1":"$00000000" }