1 / 28

Port Scanning

Port Scanning. Prabhaker Mateti. Port scanning. Attackers wish to discover services they can break into. Security audit: Why are certain ports open? sending a packet to each port, one at a time. Based on the type of response, an attacker knows if the port is used.

rod
Download Presentation

Port Scanning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Port Scanning Prabhaker Mateti

  2. Port scanning • Attackers wish to discover services they can break into. • Security audit: Why are certain ports open? • sending a packet to each port, one at a time. • Based on the type of response, an attacker knows if the port is used. • The used ports can be probed further for weakness. Mateti, Port Scanning

  3. Port Numbers • An abstraction of the OS + Net Stds • Part of UDP and TCP packets • UDP and TCP port numbers are disjoint • Typical to use the same port number for both UDP and TCP service • E.g., 80/TCP and 80/UDP for www • 16-bit unsigned integer • Well Known Ports (0 .. 1023) • Registered Ports (1024 .. 49151) • Dynamic and/or Private Ports (49152 .. 65535). • http://www.iana.org/assignments/ port-numbers Mateti, Port Scanning

  4. Sockets Mateti, Port Scanning

  5. Server socket() bind() listen() Client accept() socket() blocks until server receives a connect request from client connect negotiation connect() data write() read() data write() read() close() close() Socket calls for connection-oriented communication Mateti, Port Scanning

  6. Server socket() Client socket() bind() bind() recvfrom() blocks until server sendto() data receives data from client sendto() data recvfrom() close() close() Socket calls for connectionless communication Mateti, Port Scanning

  7. Well Known: 0 - 1023 • Only root-privileged programs are allowed to open these ports. • Examples • ftp-data 20/udp • ftp 21/tcp • ssh 22/tcp • telnet 23/tcp • Time 37/tcp • Time 37/udp • Whois 43/tcp • Imap 143/tcp Mateti, Port Scanning

  8. Registered: 1024 ..49151 • Ordinary programs/users can use these • shockwave2 1257/tcp Shockwave 2 shockwave2 1257/udp Shockwave 2 • x11 6000-6063/tcp X Window System x11 6000-6063/udp X Window System Mateti, Port Scanning

  9. Dynamic/Private: 49152 .. 65535 • Ordinary programs can use these Mateti, Port Scanning

  10. State of a Port • Open • A service process is listening at the port.  The OS receives packets arriving at this port and gives the messages to the service process.  If the OS receives a SYN at an open port, this is the first packet of the three way handshake. • Closed • No process is listening at the port.  If the OS receives a SYN at a closed port, an RST is sent. • Filtered • A packet filter is listening at the port. Mateti, Port Scanning

  11. TCP connect(0) scanning • Try connect()-ing to every port • If the port is listening, connect() will succeed. • Otherwise, the port isn’t reachable. • No need for any special privileges. Any user can use it. • Speed - slow. • Scanner can be identified. Mateti, Port Scanning

  12. TCP SYN scanning • Often referred to as half-open scanning. • Send a SYN packet • Wait for a response. • A SYN/ACK indicates the port is listening. • If a SYN/ACK is received, send an RST to tear down the connection immediately. • Most sites do not log these. • Need root privileges to build SYN packets. Mateti, Port Scanning

  13. TCP FIN Scanning • Send a FIN packet (without a preceding SYN etc.) • FIN packets may pass through firewalls • Closed ports reply with RST. • Open ports ignore the FIN packet. • Some hosts violate RFC. • Reply with RST’s regardless of the port state • Thus, are not vulnerable to this scan. Mateti, Port Scanning

  14. TCP reverse identd scanning • identd protocol (rfc1413): Disclose the username of the owner of any process connected via TCP, even if that process didn’t initiate the connection. • Example: connect to the http port (80), and then use identd to find out whether the server is running as root. • Must have full TCP connection to the port. Mateti, Port Scanning

  15. Fragmentation scanning • Not a new scanning method in and of itself. A modification of other techniques. • Split the probe packet into IP fragments. • By splitting up the TCP header over several packets, it is harder for packet filters to detect a probe. Mateti, Port Scanning

  16. FTP Bounce Scan • A port scanner can exploit this to scan TCP ports form a proxy ftp server. • Connect to an FTP server behind a firewall, and then scan ports that are more likely to be blocked. • If the ftp server allows reading from and writing to a directory (such as /incoming), you can send arbitrary data to ports that you do find open. Mateti, Port Scanning

  17. FTP Bounce Scan • Take advantage of a vulnerability of FTP protocol. • Requires support for proxy ftp connections. • For example, evil.com can establish a control communication connection to FTP server-PI (protocol interpreter) of target.com. • Then it is able to request the server-PI to initiate an active server-DTP (data transfer process) to send a file anywhere on the Internet. Mateti, Port Scanning

  18. FTP Bounce Scan • Use the PORT command (of FTP) to declare that our passive user-DTP is listening on the target box at a certain port number. • LIST the current directory, and the results is sent over the server-DTP channel. • If our target host is listening on the port, the transfer will be successful. • Otherwise, connection will be refused. • Then issue another PORT command to try the next port on the target. Mateti, Port Scanning

  19. FTP Bounce Scan • Advantages • Harder to trace • Potential to bypass firewalls. • Disadvantages • Slow • Many FTP servers have (finally) disabled the proxy feature. Mateti, Port Scanning

  20. UDP Scans • UDP is simpler, but the scanning is more difficult • Open ports do not have to send an ACK. • Closed ports are not required to send an error packet. • Most hosts send an ICMP_PORT_UNREACH error when you send a packet to a closed UDP port. • Can find out if a port is NOT open. Mateti, Port Scanning

  21. UDP Scans • Neither UDP packets, nor the ICMP errors are guaranteed to arrive. • Slow: the ICMP error message rate is limited. • Need to be root for access to raw ICMP socket. • Non-root users cannot read port unreachable errors directly. Mateti, Port Scanning

  22. UDP Scans • But users can learn it indirectly. • For example, a second write() call to a closed port will usually fail. • recvfrom() on non-blocking UDP sockets usually return EAGAIN (try again), if the ICMP error hasn’t been received. • It will return ECONNREFUSED (connection refuse), if ICMP error has been received. Mateti, Port Scanning

  23. Stealth Scan • Simple port scanning can be easily logged by the services listening at the ports. • E.g. they see an incoming connection with no data, thus they log an error. • Stealth scan refers to scanning techniques that can avoid being logged. • These techniques include fragmented packets, SYN scanning, FIN scanning etc. Mateti, Port Scanning

  24. Stealth Scan • Scan slowly • A port scanner typically scans a host too rapidly • Some detectors recognize these “signatures”. • So, scanning very slowly (e.g., over several days) is a stealth technique. • Firing packets with fake IPs • Flood with spoofed scans and embed one scan from the real source (network) address. Mateti, Port Scanning

  25. Signatures of a port scan • Several packets to different destination ports from the same source within a “short period” of time. • SYN to a non-listening port Mateti, Port Scanning

  26. Detection of Port Scanning • Open a socket • SOCK_RAW mode. • protocol type IPPROTO_IP • recvfrom() to capture the packets • Discovering stealth scans requires kernel level work. • A detector can inform us that we have been port-scanned, but the source address may have been spoofed. Mateti, Port Scanning

  27. Scanner Leaks • If the packets we received have an IP TTL of 255, we can conclude that it was sent from or local network, regardless of what the source address field says. • if TTL is 250, we can only tell that the attacker was no more than 5 hops away. Mateti, Port Scanning

  28. References • Ron Gula, How to Handle and Identify Network Probes, April 1999, www.securitywizards.com [Local Copy] Required Reading. • Hobbit, The FTP Bounce Attack,  http://www.insecure.org/nmap/ hobbit.ftpbounce.txt The original paper on the subject. Reference. • Fyodor, Remote OS detection via TCP/IP Stack Finger Printing. Written: October 18, 1998 Last Modified: April 10, 1999. http://www.insecure.org/nmap/nmap-fingerprinting-article.html   Required Reading. • Solar Designer, Designing and Attacking Port Scan Detection Tools, Phrack Magazine, Volume 8, Issue 53, July 8, 1998, article 13 of 15,  www.phrack.com .  Recommended Reading. • ZoneAlarm (download free for personal use from http://www.zonelabs.com/) that can detect port scans.  Try this on your own home network of Windows PCs. Mateti, Port Scanning

More Related