1. CIT 380: Securing Computer SystemsSlide #1 CIT 380: Securing Computer Systems Malware

2. CIT 380: Securing Computer SystemsSlide #2 Worm Components 1.Vector 2.Propagation Engine 3.Target Selection 4.Scanning Engine 5.Payload

3. CIT 380: Securing Computer SystemsSlide #3 Vector Software to gain access to target host. Common vectors: –Buffer overflow exploits. –Network file sharing, both NFS/SMB and P2P. –Social-engineering via email or IM. –Weak passwords. –Parasitism: target backdoors and worm flaws.

4. CIT 380: Securing Computer SystemsSlide #4 Propagation Engine Transfers worm to host exploited by vector. –Small worms like Slammer included in vector. Worm Propagation Methods: –FTP –HTTP –SMB –TFTP

5. CIT 380: Securing Computer SystemsSlide #5 Remote Control Interface RCI allows creator to control infected hosts. Many worms do not have a RCI. May be a well-known backdoor program. Common remote control features: Start/stop infecting new targets. Download new vectors. Download new target selectors. Download new payloads.

6. CIT 380: Securing Computer SystemsSlide #6 Target Selection Selecting targets for potential infection. E-mail address harvesting –Address books. –Parse disk files. –Search news groups. Network share enumeration –Check for filesystems shared with other systems..

7. Target Selection Network scanning –Target hosts on current network and connected nets. –Randomized scanning of Internet space. Web searching –Search Google for addresses or vulnerable software CIT 380: Securing Computer SystemsSlide #7

8. CIT 380: Securing Computer SystemsSlide #8 Scanning Engine Check targets for vulnerabilities. –If vector small, scanning can be skipped. Scan for vulnerable services. –Like targeted nmap port scan. OS Check –Check for correct OS for vector to work. Version checking. –Check version of target software. –May customize vector based on information.

9. Facebook http://www.nku.edu/~frank/cit380/docs/face book.htmhttp://www.nku.edu/~frank/cit380/docs/face book.htm CIT 380: Securing Computer SystemsSlide #9

10. Quarantine http://www.nku.edu/~frank/cit380/docs/Qua rantine.htmhttp://www.nku.edu/~frank/cit380/docs/Qua rantine.htm CIT 380: Securing Computer SystemsSlide #10

11. CIT 380: Securing Computer SystemsSlide #11 Morris Worm First Internet Worm: November 1988 Multi-architecture: Sun, VAX Multi-vector –sendmail (debug backdoor) –fingerd (buffer overflow) –rsh (open.rhosts; password cracking)

12. CIT 380: Securing Computer SystemsSlide #12 Morris Worm Spreading algorithm Local network topology: gateways, neighbors. Used users’.rhosts,.forward files. Limited reinfection rate. Detection Avoidance Forged process listing as (sh). Removed created files quickly after use.

13. CIT 380: Securing Computer SystemsSlide #13 Morris Worm Resource Requirements Disk Space. C compiler and linker. Network connection to parent computer. Problems Didn’t limit re-infections. Saturated CPU, network resources.

14. CIT 380: Securing Computer SystemsSlide #14 Malware Self-Protection Anti-debugging Detect/disable debuggers when used to analyze code. Attack anti-malware tools Disable anti-malware tools upon infection. Kill processes or destroy/modify signatures. API checksums Avoid having UNIX/Win32 API calls in code. Store checksums of API names and search for match.

15. Malware Self-Protection Code obfuscation Use unusual tricks and unused code to avoid dissassembly and prevent quick analysis of purpose. Self-modifying code. CIT 380: Securing Computer SystemsSlide #15

16. CIT 380: Securing Computer SystemsSlide #16 Self-Protection Compression Code looks almost random; size is smaller. Use unusual executable packers to avoid analysis. Data encryption Encrypt strings, hostnames, IP addresses to avoid detection.

17. Self-Protection Embedding Use multiple levels of executable packers like UPX. Scanners have to understand and have time to parse and decompress each file format. CIT 380: Securing Computer SystemsSlide #17

18. CIT 380: Securing Computer SystemsSlide #18 Self-Protection Entry-Point Obscuring Changing initial code or entry point easy to notice. Alter program code to gain control randomly. Host morphing Alter host file during infection to prevent removal.

19. CIT 380: Securing Computer SystemsSlide #19 Self-Protection: Encryption Encrypt all code except small decryptor. –Note that copy protected files will have similar decryptors to prevent analysis too. –Often uses multiple decryptors. –Change encryption key dynamically. Random Decryption Algorithm (RDA) –Choose random key for encryption. –Brute force search for key to decrypt. –Slows VMs/debuggers used for analysis.

20. CIT 380: Securing Computer SystemsSlide #20 Self-Protection: Polymorphism Alter malware code with each infection. –Cannot be detected by signature scanning. –May alter decryptor only or entire code. –Insert junk instructions that do nothing. –Fragment and rearrange order of code. –Alternate sets of instructions for the same task. Ex: SUB -1 instead of ADD 1 –Randomize names in macro viruses.

21. CIT 380: Securing Computer SystemsSlide #21 Case Study: Zmist http://en.wikipedia.org/wiki/Zmist EPO, encrypted, polymorphic virus. Code integration Decompiles PE files to smallest elements. Inserts virus randomly into existing code. Rebuilds executable. Polymorphic decryptor Inserted as random fragments linked by JMPs. Randomizes self with ETG engine.

22. CIT 380: Securing Computer SystemsSlide #22 Payloads Accidentally destructive. Replication damages data or exhausts system resources due to malware bugs. Ex: Morris Worm reinfected hosts, using all CPU. Nondestructive. Displays message, graphics, sound, or open CD door. Ex: Christma worm on IBM network in 1987. Destructive. Triggers randomly or on some event or machine type. Deletes files or overwrites data. Hardware destroyers: overwrite BIOS.

23. CIT 380: Securing Computer SystemsSlide #23 Payloads Denial of Service Sometimes accidental due to high network use. Launch DDOS attack with all infected systems. Data Theft Phishing scams and spyware. Encryptors (ransomware) Encrypts user data. Ex: One_Half encrypts disk; enables access while running. Ex: AIDS Info: encrypts disk and holds for ransom. Spam Use network of infected systems to launder spam email. Ex: Sobig worm.

24. CIT 380: Securing Computer SystemsSlide #24 Malware Interactions What happens when a virus infects a worm? Typically both propagate. May use each other’s self-protection techniques. What if anti-virus software removes a virus? Likely leaves unknown virus/worm alone. Partial removal can mutate the malware into a new form.

25. Malware Interactions Competition and Parasitism Malware may remove competing malware. May exploit backdoors/RCI left by previous malware. May infect competing malware, hijacking its propagation. CIT 380: Securing Computer SystemsSlide #25

26. CIT 380: Securing Computer SystemsSlide #26 Theory of Malicious Code Theorem 1: It is undecidable whether an arbitrary program contains a computer virus. Proof: Define virus v as TM program that copies v to other parts of the tape, while not overwriting any part of v. Reduce to Halting Problem: T’ running code V’ reproduces V iff running T on V halts. Theorem 2: It is undecidable whether an arbitrary program contains malicious logic.

27. CIT 380: Securing Computer SystemsSlide #27 Detecting Malware Signature-based –Look for known patterns in malicious code. –Defeated by polymorphic viruses. Smart scanning –Skips junk instructions inserted by poly engines. –Skips whitespace/case changes in macro viruses.

28. Detecting Malware Decryption –Brute-forces simple XOR-based encryption. –Checks decrypted text against small virus sig to decide whether has plaintext or not. CIT 380: Securing Computer SystemsSlide #28

29. CIT 380: Securing Computer SystemsSlide #29 Detecting Malware Code Emulation –Execute potential malware on VM. –Scan VM memory after certain # iterations. –Watch instructions for decryptor profile. Code Optimization. –Optimize away junk instructions and odd techniques used by polymorphic viruses.

30. CIT 380: Securing Computer SystemsSlide #30 Detecting Malware Heuristics –Code execution starts in last section. –Suspicious code redirection. –Suspicious section ACLs or size. –Suspicious library routine imports. –Hard-coded pointers into OS kernel. Neural Network Heuristics –IBM researchers trained neural net to recognize difficult polymorphic viruses. –Released in Symantec antivirus.

31. CIT 380: Securing Computer SystemsSlide #31 Detecting Malware Behavior-based –Watch for known actions from malicious code. –Network access signature of worm. –Unexpected use of dangerous system calls.

32. Detecting Malware Integrity Checking –Host-based Intrusion Detection System. –Record MAC, size, dates, ACL of files. –Periodically check for changes. –ex: Tripwire, AIDE, Osiris CIT 380: Securing Computer SystemsSlide #32

33. CIT 380: Securing Computer SystemsSlide #33 Defenses: Data vs. Code Separate data and instructions –Virus treats program as data Writes self to file. –Virus treats program as instructions Virus executes when program is run. –Solution: Treat all programs as data until trusted authority marks as executable. Development difficult when compilers can’t produce executable code.

34. CIT 380: Securing Computer SystemsSlide #34 Defenses: Information Flow Limit Information Flow –Virus executes with user’s identity. –Soln: Limit information flow between users. Set flow distance to be one for users A, B, C. A creates virus (fd=0), B executes it (fd=1). C cannot execute B’s infected program (fd=2). –Indirect virus spread limited. –How can we track information flow?

35. CIT 380: Securing Computer SystemsSlide #35 Defenses: Least Privilege Limit programs to least privilege needed example: SELinux Mail virus example 1.Virus arrives via email. 2.Virus exploits bug in email client to execute. 3.Virus saves self to file in Startup folder. 4.Virus infects Office documents. How least privilege would stop –Mail application cannot create virus binaries. –Mail application cannot write to Startup folder. –Mail application cannot write to Office documents.

36. CIT 380: Securing Computer SystemsSlide #36 Defenses: Sandboxes Execute code in protected sandbox or VM. Virtual Browser Appliance Linux guest running Firefox under VMWare. Infections can only attack VM, not real host. Reset VM to initial state if infected.

37. CIT 380: Securing Computer SystemsSlide #37 Defenses: Anomaly Detection Validate program actions with policy Limit access to system calls. Example: systrace. Check statistical characteristics. Programmer style. Compare source code with object. Statistics of write frequencies, program executions.

38. CIT 380: Securing Computer SystemsSlide #38 Defenses: Counter-worms Worm that removes other worms from net. Nachi/Welchia Multi-vector W32 worm Nachi.A removes W32/Blaster worm Nachi.B removes W32/MyDoom worm Installed MSRPC DCOM patch to prevent future infections from Blaster. Removes self after 2004. Side-effects Infected Diebold ATMs Worm traffic DOSed Internet, esp Microsoft.

39. CIT 380: Securing Computer SystemsSlide #39 Fast Worms Slammer Worm Characteristics –Attacked MS SQL servers. –Worm is single 404-byte UDP packet. –Random-scan (PRNG bugs limited.) –Limited by network bandwidth, not latency. –Observed scan rate of 26,000 hosts/second.

40. Fast Worms –Infected 90% of vulnerable hosts in 10 min. –Too fast for humans to react. –Shutdown 13,000 Bank of America ATMs due to compromising db servers, heavy traffic. CIT 380: Securing Computer SystemsSlide #40

41. CIT 380: Securing Computer SystemsSlide #41 Profitable Malware Sobig –W32 worm using email/network share vectors. –Contains upgrade mechanism Worm checked sites every few minutes. When site valid, downloaded code. Later variants could update upgrade server list. –Downloaded payload from upgrade mechanism Key logger. Wingate proxy server (for spam proxying.)

42. CIT 380: Securing Computer SystemsSlide #42 Profitable Malware Trojans Backdoor.Lala transfers authentication cookies for eBay, PayPal, etc. to maker. PWSteal.Bancos automates phishing by displaying fake web pages when browser goes to certain bank sites. Spyware and Adware More than ever using Trojan techniques. Win32/Bube virus exploits IE flaw and acts as a virus infecting IE, then downloads adware.

43. CIT 380: Securing Computer SystemsSlide #43 Mobile Malware 2004: Cabir virus infecting Symbian OS mobile phones using Bluetooth appeared in June. 2005: Commwarrior-A worm spreads to Symbian series 60 phones via phone’s MMS.

44. Mobile Malware Around a 1000 pieces of mobile malware exist. For Blackberries and Palm Pilots too. Expect more as smart phones become common. CIT 380: Securing Computer SystemsSlide #44

45. CIT 380: Securing Computer SystemsSlide #45 Offline Impact Davis-Besse nuclear power plant Slammer infected Plant Process Computer and Safety Parameter Display System (Jan 2003.) Analog backups unaffected. Infected contractor’s network, then moved through T1 line that bypassed plant firewall. Seattle 911 system Slammer disabled computer systems. Dispatchers reverted to manual systems. 2003 Blackout Blaster infected First Energy systems.

46. CIT 380: Securing Computer SystemsSlide #46 Modern Malware is Stealthy: rootkit techniques common. Targeted: targets smaller banks and countries, leverages current events: –January: Storm Worm appears via email with subject “230 dead as storm batters Europe.” –February: Miami Dolphins Stadium site hacked before superbowl so that it would infect browsers with trojan that grabbed WoW data. Blended: combine trojan, virus, worm features. Web-based: use web for delivery and update. Profit-driven: the goal is to make money.

47. CIT 380: Securing Computer SystemsSlide #47 References 1.Ross Anderson, Security Engineering, Wiley, 2001. 2.Matt Bishop, Computer Security: Art and Science, Addison-Wesley, 2003. 3.William Cheswick, Steven Bellovin, and Avriel Rubin, Firewalls and Internet Security, 2 nd edition, 2003. 4.Fred Cohen, http://www.all.net/books/virus/part1.html, 1984.http://www.all.net/books/virus/part1.html 5.Simson Garfinkel, Gene Spafford, and Alan Schartz, Practical UNIX and Internet Security, 3 rd edition, O’Reilly & Associates, 2003. 6.Alexander Gostev, “Malware Evolution: January - March 2005,” http://www.viruslist.com/en/analysis?pubid=162454316, April 18 2005. http://www.viruslist.com/en/analysis?pubid=162454316 7.Elias Levy, “Crossover: Online Pests Plaguing the Offline World,” IEEE Security & Privacy, 2003. 8.Stuart McClure, Joel Scambray, George Kurtz, Hacking Exposed, 5th edition, McGraw-Hill, 2003. 9.Hilarie Orman, “The Morris Worm: A Fifteen-Year Perspective,” IEEE Security & Privacy, 2003 10.Cyrus Peikari and Anton Chuvakin, Security Warrior, O’Reilly & Associates, 2003. 11.Ed Skoudis, Counter Hack Reloaded, Prentice Hall, 2006. 12.Ed Skoudis and Lenny Zeltser, Malware: Fighting Malicious Code, Prentice Hall, 2003. 13.Staniford, Stuart, Paxson, Vern, and Weaver, Nicholas, ‘How to 0wn the Internet in Your Spare Time,” Proceedings of the 11th USENIX Security Symposium, 2002 14.Peter Szor, The Art of Computer Virus Research and Defense, Addison-Wesley, 2005. 15.Trend Micro, “1H2007 Threat Roundup,” http://us.trendmicro.com/imperia/md/content/us/pdf/threats/securitylibrary/1h_2007_threat_round up_final_jul2007.pdf, 2007. http://us.trendmicro.com/imperia/md/content/us/pdf/threats/securitylibrary/1h_2007_threat_round up_final_jul2007.pdf