nmap scan uitgevoerd op mijn publieke ziggo IP

[mede]

Ik heb als test een poortscan met nmap (voor Windows) op mijn Ziggo IP adres uitgevoerd, maar snap de uitkomst niet helemaal.

Is er iemand hier die aan de hand van onderstaande informatie mij kan vertellen of ik enig gevaar loop?

De resultaten geven mij in eerste instantie weer (denk ik!) dat alleen "161/udp open snmp SNMPv3 server" open staat, wat waarschijnlijk iets is wat Ziggo op het Ubee modem open heeft staan?? Ik in elk geval niet.

Wat me verder opvalt is dat ik OpenVPN gebruik en daarvoor een forwarding in de Ubee modem van Ziggo heb aangemaakt naar poort 1194 (UDP). Dit geeft de poort scan niet weer???

Maar ik zie ook staan:

"Not shown: 1000 filtered ports, 999 open|filtered ports" betekent dit dat er 999 poorten open staan?

Als ik op details klik nadat de nmap scan klaar is zie ik het volgende:



Ik heb mijn IP/hostname vervangen in onderstaande output

code:

Starting Nmap 6.46 ( http://nmap.org ) at 2014-04-28 11:34 W. Europe Daylight Time

NSE: Loaded 118 scripts for scanning.

NSE: Script Pre-scanning.

Initiating Ping Scan at 11:34

Scanning [MY_DDNS_HOST_NAME] (MY_ISP_IP) [4 ports]

Completed Ping Scan at 11:34, 0.20s elapsed (1 total hosts)

Initiating Parallel DNS resolution of 1 host. at 11:34

Completed Parallel DNS resolution of 1 host. at 11:34, 0.00s elapsed

Initiating SYN Stealth Scan at 11:34

Scanning MY_DDNS_HOST_NAME (MY_ISP_IP) [1000 ports]

Completed SYN Stealth Scan at 11:34, 4.04s elapsed (1000 total ports)

Initiating UDP Scan at 11:34

Scanning MY_DDNS_HOST_NAME (MY_ISP_IP) [1000 ports]

[b]Discovered open port 161/udp on MY_ISP_IP[/b]

Completed UDP Scan at 11:34, 4.02s elapsed (1000 total ports)

Initiating Service scan at 11:34

Scanning 1000 services on MY_DDNS_HOST_NAME (MY_ISP_IP)

Service scan Timing: About 0.40% done

Service scan Timing: About 3.20% done; ETC: 13:00 (1:23:11 remaining)

Service scan Timing: About 6.20% done; ETC: 12:41 (1:02:32 remaining)

Service scan Timing: About 9.20% done; ETC: 12:34 (0:54:17 remaining)

Service scan Timing: About 12.20% done; ETC: 12:30 (0:49:32 remaining)

Service scan Timing: About 15.20% done; ETC: 12:28 (0:46:02 remaining)

Service scan Timing: About 18.20% done; ETC: 12:27 (0:43:18 remaining)

Service scan Timing: About 23.90% done; ETC: 12:20 (0:35:17 remaining)

Service scan Timing: About 24.20% done; ETC: 12:25 (0:38:47 remaining)

Service scan Timing: About 29.80% done; ETC: 12:20 (0:32:35 remaining)

Service scan Timing: About 30.20% done; ETC: 12:24 (0:34:59 remaining)

Service scan Timing: About 35.80% done; ETC: 12:20 (0:29:44 remaining)

Service scan Timing: About 41.80% done; ETC: 12:20 (0:26:55 remaining)

Service scan Timing: About 47.80% done; ETC: 12:20 (0:24:07 remaining)

Service scan Timing: About 53.80% done; ETC: 12:20 (0:21:20 remaining)

Service scan Timing: About 59.80% done; ETC: 12:20 (0:18:33 remaining)

Service scan Timing: About 65.80% done; ETC: 12:20 (0:15:46 remaining)

Service scan Timing: About 71.70% done; ETC: 12:20 (0:13:03 remaining)

Service scan Timing: About 77.70% done; ETC: 12:20 (0:10:17 remaining)

Service scan Timing: About 83.70% done; ETC: 12:20 (0:07:31 remaining)

Service scan Timing: About 89.20% done; ETC: 12:20 (0:05:00 remaining)

Service scan Timing: About 95.20% done; ETC: 12:20 (0:02:13 remaining)

Completed Service scan at 12:21, 2805.37s elapsed (1000 services on 1 host)

Initiating OS detection (try #1) against MY_DDNS_HOST_NAME (MY_ISP_IP)

Retrying OS detection (try #2) against MY_DDNS_HOST_NAME (MY_ISP_IP)

Initiating Traceroute at 12:21

Completed Traceroute at 12:21, 0.01s elapsed

NSE: Script scanning MY_ISP_IP.

Initiating NSE at 12:21

NSE Timing: About 0.40% done

NSE Timing: About 2.44% done; ETC: 13:03 (0:40:40 remaining)

NSE Timing: About 4.44% done; ETC: 12:55 (0:32:38 remaining)

NSE Timing: About 6.47% done; ETC: 12:52 (0:29:10 remaining)

NSE Timing: About 8.49% done; ETC: 12:50 (0:27:07 remaining)

NSE Timing: About 10.62% done; ETC: 12:49 (0:25:24 remaining)

NSE Timing: About 14.48% done; ETC: 12:45 (0:21:04 remaining)

NSE Timing: About 20.66% done; ETC: 12:45 (0:19:28 remaining)

NSE Timing: About 26.74% done; ETC: 12:45 (0:18:00 remaining)

NSE Timing: About 31.56% done; ETC: 12:45 (0:16:37 remaining)

NSE Timing: About 37.84% done; ETC: 12:45 (0:15:09 remaining)

NSE Timing: About 43.92% done; ETC: 12:45 (0:13:41 remaining)

NSE Timing: About 49.42% done; ETC: 12:45 (0:12:24 remaining)

NSE Timing: About 54.25% done; ETC: 12:45 (0:11:09 remaining)

NSE Timing: About 59.56% done; ETC: 12:45 (0:09:56 remaining)

NSE Timing: About 64.48% done; ETC: 12:45 (0:08:39 remaining)

NSE Timing: About 69.98% done; ETC: 12:45 (0:07:23 remaining)

NSE Timing: About 75.10% done; ETC: 12:45 (0:06:04 remaining)

NSE Timing: About 80.41% done; ETC: 12:45 (0:04:48 remaining)

NSE Timing: About 86.29% done; ETC: 12:45 (0:03:22 remaining)

NSE Timing: About 91.41% done; ETC: 12:45 (0:02:06 remaining)

NSE Timing: About 96.62% done; ETC: 12:45 (0:00:50 remaining)

Completed NSE at 12:45, 1479.65s elapsed

Nmap scan report for MY_DDNS_HOST_NAME (MY_ISP_IP)

NSOCK ERROR [3531.1490s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #518): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)

NSOCK ERROR [3532.3120s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #521): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)

NSOCK ERROR [3533.4770s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #522): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)

NSOCK ERROR [3534.6520s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #523): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)

NSOCK ERROR [3797.5510s] mksock_bind_addr(): Bind to 0.0.0.0:123 failed (IOD #703): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)

NSOCK ERROR [4260.0070s] mksock_bind_addr(): Bind to 0.0.0.0:443 failed (IOD #1036): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)

Host is up (0.0014s latency).

rDNS record for MY_ISP_IP: MY_ZIGGO_DNS-NAME.dynamic.ziggo.nl

[b]Not shown: 1000 filtered ports, 999 open|filtered ports[/b]

PORT    STATE SERVICE VERSION

[b]161/udp open  snmp    SNMPv3 server[/b]

|_snmp-hh3c-logins: TIMEOUT

|_snmp-win32-shares: TIMEOUT

1 service unrecognized despite returning data. If you know the service/version, please submit the following fingerprint at http://www.insecure.org/cgi-bin/servicefp-submit.cgi :

SF-Port161-UDP:V=6.46%I=7%D=4/28%Time=535E20AE%P=i686-pc-windows-windows%r

SF:(SNMPv3GetRequest,66,"0d\x02\x01\x030\x0e\x02\x02Ji\x02\x02\x05x\x04\x0

SF:1\0\x02\x01\x03\x04\x1e0\x1c\x04\x0c\x80\0\x12L\x05\x88\x9f\xfa\xd3l\xc

SF:43\x02\x01-\x02\x03\x02\x99!\x04\0\x04\0\x04\x000/\x04\x0c\x80\0\x12L\x

SF:05\x88\x9f\xfa\xd3l\xc43\x04\0\xa8\x1d\x02\x027\xf0\x02\x01\0\x02\x01\x

SF:000\x110\x0f\x06\n\+\x06\x01\x06\x03\x0f\x01\x01\x04\0A\x01\x02");

Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port

Aggressive OS guesses: Linux 2.6.18 (94%), Apple Mac OS X 10.7.4 (Lion) (Darwin 11.4.0) (93%), Aruba IAP-93 WAP (93%), Cisco 4402 wireless LAN controller (93%), Citrix Access Gateway VPN gateway (93%), Epson Artisan 810 printer (93%), HP OpenVMS 7.3 (93%), Juniper SA2500 SSL VPN gateway (93%), Linksys RV042 router (93%), Linux 2.6.11 (93%)

No exact OS matches for host (test conditions non-ideal).

Network Distance: 1 hop



TRACEROUTE (using port 80/tcp)

HOP RTT     ADDRESS

1   1.00 ms MY_ZIGGO_DNS-NAME.dynamic.ziggo.nl (MY_ISP_IP)



NSE: Script Post-scanning.

Read data files from: C:\Program Files (x86)\Nmap

OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .

Nmap done: 1 IP address (1 host up) scanned in 4310.63 seconds

Raw packets sent: 4060 (152.510KB) | Rcvd: 19 (1.444KB)

[InFamous]

Je foto plaatje doet het niet.

[ Voor 33% gewijzigd door InFamous op 28-04-2014 19:27 ]

[LnC]

Wat je ook kan doen is een scan laten uitvoeren door de website Shields Up!
Je kan hierop verschillende poorten laten scannen (ook specifieke).

Met de uitkomst van deze website kan je die naast je eerdere uitkomsten van Nmap vergelijken.

[LuckY]

Vanaf waar heb je gescanned?
Want als je lokaal scanned kan je soms te maken krijgen met 'NAT-hairpinning'/'NAT-loopback'.
Probeer het eens vanaf een ander netwerk?