| SG Security Scan |
| Scanning 38.103.63.18 (38.103.63.18): |
| Not shown: 38 closed ports |
| Port | Status | Service | Description |
| 113/tcp |
open |
auth |
Port 113 used for Identification/Authorization service. When a client program on your end contacts a remote server for services such as POP, IMAP, SMTP, IRC, FTP, etc. that remote server sends back a query to the IDENT port 113 asking for identification from your system...
Port 113 can be probed by attackers and it poses some security concerns, but the problem with filtering/stealthing port 113 is that if legitimate requests get no response at all from port 113 queries, the connection to them (which initiated their query in the first place) will be delayed or perhaps even completely abandoned.
The simplest solution is to close, rather than filter port 113.
Some trojans also use this port: ADM worm, Alicia, Cyn, DataSpy Network X, Dosh, Gibbon, Invisible Identd Deamon, Kazimas, Taskman
W32.Bofra.C@mm (11.11.2004) - It opens ports 1639/tcp and 1640/tcp for listening, opens an ident daemon on port 113/tcp, connects to IRC servers on port 6667/tcp.
W32.Linkbot.A (11.05.2004) - worm that exploits the MS Windows LSASS Buffer Overrun Vulnerability. It also creates an IRC backdoor and attempts to install adware on the infected machine. It can affect all current Windows versions. Listens on port 113/tcp for remote commands.
W32.Spybot.LZI (04.06.2005) - worm that attempts to exploit the MS DCOM RPC vulnerability on ports 135, 445 & 1025. Opens a backdoor on port 113.
W32.Linkbot.M (05.24.2005) - opens a backdoor on port 6667/tcp. Also listens on port 113/tcp. |
| 20/udp |
filtered? |
ftp-data |
|
| 21/udp |
filtered? |
ftp |
FSP/FTP |
| 22/udp |
filtered? |
ssh |
Old verson of pcAnywhere uses port 22/udp (no relation to ssh and port 22/tcp).
The real pcAnywhere port is 5632. The value 0x0016 (hex) is 22 decimal; the value of 0x1600 (hex) is 5632 decimal. Some say that pcAnywhere had a byte-swapping bug that led to its incorrect use of port 22. |
| 49/udp |
filtered? |
tacacs |
Login Host Protocol (TACACS) |
| 53/udp |
filtered? |
domain |
DNS (Domain Name Service) is used for domain name resolution.
There are some attacks that target vulnerabilities within DNS servers. Some trojans also use this port: ADM worm, li0n, MscanWorm, MuSka52, Trojan.Esteem.C (05.12.2005), W32.Spybot.ABDO (12.12.2005).
W32.Dasher.B (12.16.2005) - a worm that exploits the MS Distributed Transaction Coordinator Remote exploit (MS Security Bulletin MS05-051).
Listens for remote commands on port 53/tcp. Connects to an FTP server on port 21211/tcp. Scans for systems vulnerable to the MS05-051 exploit on port 1025/tcp. |
| 99/udp |
filtered? |
metagram |
metagram relay, gnutella? |
| 110/udp |
filtered? |
pop3 |
POP3 server traffic (should be TCP only?) |
| 111/udp |
filtered? |
rpcbind |
Provides information between Unix based systems. Port is often probed, it can be used to fingerprint the Nix OS, and to obtain information about available services. Port used with NFS, NIS, or any rpc-based service.
Trojans that use this port: ADM worm, MscanWorm |
| 119/udp |
filtered? |
nntp |
NNTP (Network News Transfer Protocol) control messages. |
| 123/udp |
filtered? |
ntp |
Network Time Protocol (NTP) |
| 137/udp |
filtered? |
netbios-ns |
NetBIOS is a protocol used for File and Print Sharing under all current versions of Windows. While this in itself is not a problem, the way that the protocol is implemented can be.
NetBios services:
NETBIOS Name Service (TCP/UDP: 137)
NETBIOS Datagram Service (TCP/UDP: 138)
NETBIOS Session Service (TCP/UDP: 139)
By default, when File and Print Sharing is enabled it binds to everything, including TCP/IP (The Internet Protocol), rather than just the local network, meaning your shared resources are available over the entire Internet for reading and deletion, unless configured properly. Any machine with NetBIOS enabled and not configured properly should be considered at risk. The best protection is to turn off File and Print Sharing, or block ports 135-139 completely. If you must enable it, use the following guidelines:
1. Use strong passwords, containing non-alphanumeric characters.
2. Attach "$" at the end of your share names (the casual snooper using net view might not see them).
3. Unbind File and Print Sharing from TCP/IP and use NetBEUI instead (it's a non-routable protocol).
4. Block ports 135-139 in your router/firewall.
Keep in mind that you might still be leaking out information about your system that can be used against you (such as your computer and workgroup names) to the entire Internet, unless ports are filtered by a firewall.
There is also a Critical Windows RPC vulnerability affecting ports 135,139 and 445, as detailed here: MS Technet Security Bulletin MS03-026
The following trojans/backdoors also use these ports: Chode, God Message worm, Msinit, Netlog, Network, Qaz
W32.HLLW.Moega
W32.Crowt.A@mm (01.23.2005) - mass mailing worm, opens a backdoor, logs keystrokes. Uses ports 80 and 137.
W32.Reidana.A (03.27.2005) - worm that spreads using the MS DCOM RPC vulnerability (MS Security Bulletin MS03-026) on port 139. The worm attempts to download and execute a remote file via FTP. Opens TCP port 4444. |
| 138/udp |
filtered? |
netbios-dgm |
same as port 137/udp |
| 139/udp |
filtered? |
netbios-ssn |
same as port 137/udp |
| 143/udp |
filtered? |
imap |
IMAP mail server uses this port. See also port 993/tcp.
Numerous IMAP servers have buffer overflows that allow compromise during the login. Note that for awhile, there was a Linux worm (admw0rm) that would spread by compromising port 143, so a lot of scans on this port are actually from innocent people who have already been compromised. IMAP exploits became popular when Red Hat enabled the service by default on its distributions. This port is also used for IMAP2, but that version wasn't very popular. Several people have noted attacks from port 0 to port 143, which appears to be from some attack script. |
| 161/udp |
filtered? |
snmp |
Simple network management protocol (SNMP). Used by various devices and applications (including firewalls and routers) to communicate logging and management information with remote monitoring applications.
Typically, SNMP agents listen on UDP port 161, asynchronous traps are received on port 162. |
| 162/udp |
filtered? |
snmptrap |
same as port 161/udp |
| 1026/udp |
filtered? |
unknown |
Ports > 1024 are designated for dynamic allocation by Windows. When programs ask for the "next available" socket, they usually get sequential ports starting at 1025.
Ports 1026/udp - 1027/udp are usually used by Messenger Popup Spam as well. |
| 1027/udp |
filtered? |
unknown |
same as port 1026/udp |
| 1028/udp |
filtered? |
ms-lsa |
same as port 1026/udp |
| 1029/udp |
filtered? |
unknown |
same as port 1026/udp |
| 1863/udp |
filtered? |
unknown |
Port used by MSN Messenger
W32.Mytob.IE@mm (07.26.2005) - a mass-mailing worm that opens a backdoor and lowers security settings on the compromised computer. It uses its own SMTP engine. Opens a backdoor and listens for remote commands on port 1863/tcp. |
| 5678/udp |
filtered? |
unknown |
Port used by Linksys (and other) Cable/DSL Routers Remote Administration
Vulnerable systems: Linksys Cable/DSL version 1.42.7 (BEFSR11 / BEFSR41 / BEFSRU31)
Immune systems: Linksys Cable/DSL versions prior to 1.42.7 (BEFSR11 / BEFSR41 / BEFSRU31)
|
| 27374/udp |
filtered? |
unknown |
SubSeven Trojan horse (TCP). Also used as a backdoor port left behind by exploit scripts, such as those in the Ramen worm. While some scans for this port may be due to SubSeven, others may be looking for a remote shell.
Some other trojan horses/backdoors that use this port: Bad Blood, Ramen, Seeker, SubSeven (many versions), Ttfloader |
| Total scanned ports: | 62 |
| Open ports: | 1 |
| Closed ports: | 38 |
| Filtered ports: | 23 |
| Login (or register free) for a more detailed security scan. |
| 1 open ports found on your system ! |
|
The Security Scan found open ports on my system, now what ?
First, read the descriptions carefully. It could be a trojan, or you may have some other service running on that port.
For instance, Web servers listen on port 80 in addition to the listed trojans for the same port.
So, now that some ports show open (accepting connections and potentialy vulnerable to attacks), you will have to
look into what is running on your system that accepted our probe. We try to cover the most common services using
the ports we scan. Please read the Security FAQ, and visit our security forum for additional help.
|
| Port Status Legend |
| open |
Open ports offer services that are potentialy vulnerable to attacks! All ports should be closed or filtered, unless you specifically require some open (and know exactly what they are). |
| closed |
Ports in this category respond to our scan, however appear to be closed. This state offers medium security. It still reveals that your system is up, and might provide some additional fingerprinting information to potential intruders. |
| filtered |
Filtered ports do not respond to a portscan at all, they don't appear to exist. This is the best security level for your ports, as it provides no information about your system or its existence (a.k.a. black hole). |
filtered?
open|filtered |
Filtered UDP ports that do not respond to the scan.
Note that the UDP protocol is not lossless, and does not respond to all requests by definition.
Therefore, the lack of response does not guarantee that a port is being filtered.
We have send a few requests without response, and it is reasonable to believe the ports
in this state are filtered.
|
