24-11-2011, 03:03 AM
I was screwing around today with "nmap" port scanning tool. I was scanning port 162 on coax side IP addresses such as 10.11.22.1 ~> 10.11.22.254
.
I got quite a few hits in the range:
.
.
.
Next I ran snmpwalk on a few of the IP's to see if any of them responded. A couple of them did! The ones that didn't were usually Motorola or Scientific modems (I checked with a web browser)
.
.
I also tried port 161 on a few of the Motorola modems....no luck. The modems that responded were Toshiba.
.
.
So it appears that not all modems are immune (but most) to snmp in this area. BTW, the Toshiba modems haven't had a firmware update since 2005. Well, that was fun.
Code:
bash-4.1#nmap 10.11.22.1-254 -p162 -sU --open
I got quite a few hits in the range:
.
Code:
Nmap scan report for 10.11.22.34
Host is up (0.65s latency).
PORT STATE SERVICE
162/udp open|filtered snmptrap
.
Next I ran snmpwalk on a few of the IP's to see if any of them responded. A couple of them did! The ones that didn't were usually Motorola or Scientific modems (I checked with a web browser)
.
Code:
bash-4.1 snmpwalk -v2c -c public 10.11.22.34:162 1.3.1
I also tried port 161 on a few of the Motorola modems....no luck. The modems that responded were Toshiba.
.
Code:
SNMPv2-SMI::mib-2.47.1.1.1.1.10.1 = STRING: "3.0.14"
SNMPv2-SMI::mib-2.47.1.1.1.1.11.1 = STRING: "2411533960"
SNMPv2-SMI::mib-2.47.1.1.1.1.12.1 = STRING: "Toshiba Corporation"
SNMPv2-SMI::mib-2.47.1.1.1.1.13.1 = STRING: "PCX2600"
So it appears that not all modems are immune (but most) to snmp in this area. BTW, the Toshiba modems haven't had a firmware update since 2005. Well, that was fun.