Explizit gefilterte Ports bei Border-Routern

2 Beiträge08.06.2006Archiviert
Marc Ruef08.06.2006 · Beitrag #7916
Admin
Avatar
Mitglied seit: 25.01.2005
Forenbeiträge: 1337
Besuche: 22158
Hallo,

Ich habe vor einiger Zeit einen Penetration Test bei einem Schweizer Kunden durchgefuehrt. Dieser benutzte einen Border-Router, der vom ISP (Cybernet) bereitgestellt wurde.

Dabei ist mir einmal mehr aufgefallen, dass einige populaere Ports explizit Anfragen droppen:

[command]Starting Nmap 4.00 ( http://www.insecure.org/nmap/ ) at 2006-xx-xx 01:23 CEST
DNS resolution of 1 IPs took 0.01s. Mode: Async [#: 3, OK: 1, NX: 0, DR: 0, SF: 0, TR: 1, CN: 0]
Initiating SYN Stealth Scan against adsl-x-x-x-x.cybernet.ch (x.x.x.x) [1672 ports] at 01:23
The SYN Stealth Scan took 7.45s to scan 1672 total ports.
Warning: OS detection will be MUCH less reliable because we did not find at least 1 open and 1 closed TCP port
Host adsl-x-x-x-x.cybernet.ch (x.x.x.x) appears to be up ... good.
Interesting ports on adsl-x-x-x-x.cybernet.ch (x.x.x.x):
(The 1658 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE VERSION
21/tcp filtered ftp
23/tcp filtered telnet
80/tcp filtered http
135/tcp filtered msrpc
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
515/tcp filtered printer
593/tcp filtered http-rpc-epmap
1025/tcp filtered NFS-or-IIS
1433/tcp filtered ms-sql-s
1434/tcp filtered ms-sql-m
3128/tcp filtered squid-http
Too many fingerprints match this host to give specific OS details
TCP/IP fingerprint:
SInfo(V=4.00%P=x86_64-unknown-linux-gnu%D=5/5%Tm=445A8D12%O=-1%C=1)
T5(Resp=Y%DF=N%W=0%ACK=S++%Flags=AR%Ops=)
T6(Resp=Y%DF=N%W=0%ACK=O%Flags=R%Ops=)
T7(Resp=Y%DF=N%W=0%ACK=S%Flags=AR%Ops=)
PU(Resp=Y%DF=N%TOS=0%IPLEN=38%RIPTL=148%RID=E%RIPCK=E%UCK=E%ULEN=134%DAT=E)

Nmap finished: 1 IP address (1 host up) scanned in 12.100 seconds
Raw packets sent: 1724 (70KB) | Rcvd: 1670 (76.8KB)[/command]

Das OS-Fingerprinting mit Xprobe2 und manuelle Verifikationen lassen Cisco IOS 12.2 vermuten:

[command]Xprobe2 v.0.3 Copyright (c) 2002-2005 [email protected], [email protected], [email protected]

[+] Target is x.x.x.x
[+] Loading modules.
[+] Following modules are loaded:
[x] [1] ping:icmp_ping - ICMP echo discovery module
[x] [2] ping:tcp_ping - TCP-based ping discovery module
[x] [3] ping:udp_ping - UDP-based ping discovery module
[x] [4] infogather:ttl_calc - TCP and UDP based TTL distance calculation
[x] [5] infogather:portscan - TCP and UDP PortScanner
[x] [6] fingerprint:icmp_echo - ICMP Echo request fingerprinting module
[x] [7] fingerprint:icmp_tstamp - ICMP Timestamp request fingerprinting module
[x] [8] fingerprint:icmp_amask - ICMP Address mask request fingerprinting module
[x] [9] fingerprint:icmp_port_unreach - ICMP port unreachable fingerprinting module
[x] [10] fingerprint:tcp_hshake - TCP Handshake fingerprinting module
[x] [11] fingerprint:tcp_rst - TCP RST fingerprinting module
[x] [12] fingerprint:smb - SMB fingerprinting module
[x] [13] fingerprint:snmp - SNMPv2c fingerprinting module
[+] 13 modules registered
[+] Initializing scan engine
[+] Running scan engine
[-] ping:tcp_ping module: no closed/open TCP ports known on x.x.x.x. Module test failed
[-] ping:udp_ping module: no closed/open UDP ports known on x.x.x.x. Module test failed
[-] No distance calculation. x.x.x.x appears to be dead or no ports known
[+] Host: x.x.x.x is up (Guess probability: 50%)
[+] Target: x.x.x.x is alive. Round-Trip Time: 0.04114 sec
[+] Selected safe Round-Trip Time value is: 0.08227 sec
[-] fingerprint:tcp_hshake Module execution aborted (no open TCP ports known)
[-] fingerprint:smb need either TCP port 139 or 445 to run
[+] Primary guess:
[+] Host x.x.x.x Running OS: "Cisco IOS 11.2" (Guess probability: 95%)
[+] Other guesses:
[+] Host x.x.x.x Running OS: "Cisco IOS 11.1" (Guess probability: 95%)
[+] Host x.x.x.x Running OS: "HP JetDirect ROM G.07.02 EEPROM G.08.04" (Guess probability: 91%)
[+] Host x.x.x.x Running OS: "HP JetDirect ROM F.08.08 EEPROM F.08.20" (Guess probability: 91%)
[+] Host x.x.x.x Running OS: "Microsoft Windows NT 4 Workstation Service Pack 5" (Guess probability: 95%)
[+] Host x.x.x.x Running OS: "NetBSD 1.6.2" (Guess probability: 95%)
[+] Host x.x.x.x Running OS: "NetBSD 1.5.2" (Guess probability: 95%)
[+] Host x.x.x.x Running OS: "NetBSD 1.4.2" (Guess probability: 95%)
[+] Host x.x.x.x Running OS: "Microsoft Windows NT 4 Server Service Pack 4" (Guess probability: 95%)
[+] Host x.x.x.x Running OS: "HP JetDirect ROM G.07.19 EEPROM G.08.04" (Guess probability: 95%)
[+] Cleaning up scan engine
[+] Modules deinitialized
[+] Execution completed.[/command]

Meine Frage bezieht sich auf die expliziten Drops fuer die populaeren Ports wie 21, 80 oder 135. Wird dies wohl umgesetzt, um bei automatisierten (Wurm-)Attacken moeglichst wenig belastenden Traffic zu verursachen?

Bye, Marc
padrino08.06.2006 · Beitrag #7917
Mitglied seit: 13.09.2005
Forenbeiträge: 267
Besuche: 2452
balcab (heute cablecom) hatte einst den port 80 gesperrt, damit die kunden nicht hosting-provider spielten und zu viel traffic generierten. vielleicht wollen sie den kunden ebenfalls ein wenig einschränken. wobei bei diesem cybernet-kunden ist smtp nicht blockiert ... das mit dem einschränken wird wohl eher nicht zutreffen, wäre sonst jedoch eine variante, falls das wieder über den weg läuft.
könnt gut sein um schaden bei wurm-ausbrüchen einzudämmen. würde sinn ergeben.

tschau


padrino