Crisis And Aftermath Eugene H. Spafford 이희범.  Introduction  How the worm operated  Aftermath Contents.

Slides:



Advertisements
Similar presentations
Buffer Overflows Nick Feamster CS 6262 Spring 2009 (credit to Vitaly S. from UT for slides)
Advertisements

Computer Science CSC 405Dr. Peng Ning1 CSC 405 Introduction to Computer Security Topic 3. Program Security -- Part I.
Slide 2-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 2 Using the Operating System 2.
C risis And A ftermath Eugene H. Spafford 발표자 : 손유민.
Communications of the ACM (CACM), Vol. 32, No. 6, June 1989
Lecture: Malicious Code CIS 3360 Ratan K. Guha. Malicious Code2 Overview and Reading Assignments Defining malicious logic Types Action by Viruses Reading.
Utilizing the GDB debugger to analyze programs Background and application.
CSE331: Introduction to Networks and Security Lecture 32 Fall 2002.
Using tcpdump. tcpdump is a powerful tool that allows us to sniff network packets and make some statistical analysis out of those dumps. tcpdump operates.
October 15, 2002Serguei A. Mokhov, 1 UNIX Security 2: A Quick Recap SOEN321 - Information Systems Security Revision 1.3 Date: September.
Telnet and FTP. Telnet Lets you use the resources of some other computer on the Internet to access files, run programs, etc. Creates interactive connection.
Silberschatz, Galvin and Gagne  Operating System Concepts The Security Problem A system is secure iff its resources are used and accessed as.
Secure Shell – SSH Tam Ngo Steve Licking cs265. Overview Introduction Brief History and Background of SSH Differences between SSH-1 and SSH- 2 Brief Overview.
Security A system is secure if its resources are used and accessed as intended under all circumstances. It is not generally possible to achieve total security.
Eugene H. Spafford, "The Internet Worm Program: An Analysis" Presented by Petko Bakalov University of California - Riverside
Introducing the Command Line CMSC 121 Introduction to UNIX Much of the material in these slides was taken from Dan Hood’s CMSC 121 Lecture Notes.
CSCE 515: Computer Network Programming Chin-Tser Huang University of South Carolina.
The Internet Worm Crisis and Aftermath Miyu Nakagawa Cameron Smithers Ying Han.
Working Environment - - Linux - -.
SSH : The Secure Shell By Rachana Maheswari CS265 Spring 2003.
Lecture 11, : The Internet, Summer : The Internet Lecture 11: Secure services David O’Hallaron School of Computer Science and Department.
© 2007 Pearson Education Inc., Upper Saddle River, NJ. All rights reserved.1 Computer Networks and Internets with Internet Applications, 4e By Douglas.
Overview Computer security threats Unintentional:
Chapter 26 remote logging & Ftp
TCP Sockets Reliable Communication. TCP As mentioned before, TCP sits on top of other layers (IP, hardware) and implements Reliability In-order delivery.
13.1 Silberschatz, Galvin and Gagne ©2011 Operating System Concepts Essentials – 8 th Edition Security.
Computation for Physics 計算物理概論 Introduction to Linux.
Help session: Unix basics Keith 9/9/2011. Login in Unix lab  User name: ug0xx Password: ece321 (initial)  The password will not be displayed on the.
Security Exploiting Overflows. Introduction r See the following link for more info: operating-systems-and-applications-in-
Applications: Remote Login (TELNET,Rlogin) In this chapter we shall explore internetworking by examining high level internet services and protocols that.
Attacks Let us start by looking at traditional attack types. Address spoofing (=cheating) This is a set of attacks where the attacker sets to IP or TCP.
Chapter 10 Networking and the Internet ITSC 1458.
Understanding the CORBA Model. What is CORBA?  The Common Object Request Broker Architecture (CORBA) allows distributed applications to interoperate.
Simple Mail Transfer Protocol (SMTP)
CMSC 414 Computer (and Network) Security Lecture 14 Jonathan Katz.
More Network Security Threats Worm = a stand-alone program that can replicate itself and spread Worms can also contain manipulation routines to perform.
Administrative: Objective: –Tutorial on Risks –Phoenix recovery Outline for today.
Bugs SATAN scans for It is interesting to look at the bugs SATAN scans for. They are easily detected by the scanners and therefore do not pose a threat.
Department of Computer Science Southern Illinois University Edwardsville Spring, 2008 Dr. Hiroshi Fujinoki FTP Protocol Programming.
Hour 7 The Application Layer 1. What Is the Application Layer? The Application layer is the top layer in TCP/IP's protocol suite Some of the components.
Cracking Techniques Onno W. Purbo
CH 25-Remote Login (TELNET,Rlogin)
©Ian Sommerville 2004Software Engineering Case Studies Slide 1 The Internet Worm Compromising the availability and reliability of systems through security.
Topics Network topology Virtual LAN Port scanners and utilities Packet sniffers Weak protocols Practical exercise.
1 Chapter 34 Internet Applications (Telnet, FTP).
Processes CSCI 4534 Chapter 4. Introduction Early computer systems allowed one program to be executed at a time –The program had complete control of the.
Programmed Threats Richard Newman. What is a Programmed Threat? Potential source of harm from computer code May be in form of - Executable program - Executable.
4061 Session 26 (4/19). Today Network security Sockets: building a server.
A Failure to Learn from the Past Presented by Chad Frommeyer CSC 493/593 Professors Charles E. Frank/James Walden.
Introduction to UNIX CS 2204 Class meeting 1 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright
The Internet Worm Incident Eugene H. Spafford  Attack Format –Worm vs. Virus  Attack Specifications –Worm operation –Infection and propagaion  Topics.
Information Security - 2. A Stack Frame. Pushed to stack on function CALL The return address is copied to the CPU Instruction Pointer when the function.
Application of the Internet 1998/12/09 KEIO University, JAPAN Mikiyo
Ch26 Ameera Almasoud 1 Based on Data Communications and Networking, 4th Edition. by Behrouz A. Forouzan, McGraw-Hill Companies, Inc., 2007.
Week-2 (Lecture-1) An electronic message sent from one computer to another. contains account i.e. How does.
Network Attacks Instructor: Dr. X. Outline Worms DoS.
Chapter 7: Using Network Clients The Complete Guide To Linux System Administration.
The Internet Worm Compromising the availability and reliability of systems through security failure.
FTP Lecture supp.
Onno W. Purbo Cracking Techniques Onno W. Purbo
Module 4 Remote Login.
A Guide to Unix Using Linux Fourth Edition
FTP - File Transfer Protocol
(Chapter 2) John Carelli, Instructor Kutztown University
Internet Worms, SYN DOS attack
Remote Computing Services Cloud connection Distributed system
Crisis and Aftermath Eugene H. Spafford
Crisis and Aftermath Morris worm.
Understanding and Preventing Buffer Overflow Attacks in Unix
Internet Applications (Telnet, FTP)
Presentation transcript:

Crisis And Aftermath Eugene H. Spafford 이희범

 Introduction  How the worm operated  Aftermath Contents

Introduction

Worm vs. Virus WormVirus Can run independently?YesNo How this operated?Consume the resource of its host Insert itself into a host’s some program When invoked?ItselfWhen infected program is running TargetSeveral systemsTarget machine

 On the evening of November 2, 1988 MIT  Infect Sun 3 systems and VAX computer running variants of 4 BSD UNIX  Systems became so loaded that they were unable to continue any processing. Morris Worm

 The worm took advantage of some flaws in standard software installed on UNIX. (fingerd, sendmail)  It also took advantage of a mechanism used to simplify the sharing of resources in local area networks (rsh, rexec) How the worm operated

 finger : allows user to obtain information about other user over TPC(79)/IP Common Unix systems run a demon of finger (fingerd) The worm broke fingerd program by “buffer overflow” The worm exploited gets() (no bound checking) call Fingerd

 sendmail is mailer program to route mail in a heterogeneous network.  By debug option, tester can run programs to display the state of the mail system without sending mail or establishing a separate login connection.  Worm uses debug option to invoke set of commands instead of user address Sendmail

 rsh and rexec are remote command execution services.  rsh (client IP, user ID)  rexec (user ID, Password) rsh, rexec

 Password mechanism in UNIX system 1. Insert password 2. “Encryption standard algorithm” encrypted 3. Compare with Previously encrypted password 4. If it is same, we get a accessibility Password

 Multiple processor and processor speed up  Tendency of users to choose common words as their passwords  Ways to reduce the risk of such attacks Shadow file Time delay and Threshold Change utility Password

 Main Program : collect information on other machines in the network and attack  Vector Program : Program which install main program Worm

 Rsh – simply try and success cases Remote machine had a hosts.equiv file or The user had a.rhosts file  Rexec – if worm knows password Simply try Users often have the same password on their accounts on muiltiple machines Attack method(1)

1. Collect info /etc/hosts.equiv and /.rhosts /etc/passwd.forward 2. Cracking passwd using simple choices 3. Cracking passwd with an internal dictionary of words 4. Cracking passwd with /usr/dict/words Cracking Password

 Fingerd – 1.connection 2. input 3. output Transmit specially constructed string of 536bytes Stack overflow attacking Change the return stack frame for main execve(“/bin/sh”, 0, 0) Attack method(2)

 Sendmail Use debug mode Transmit command instead of recv address Attack method(3)

 A socket was established  Magic number was generated  Random file name was generated Step 1

PATH=/bin: /usr/bin: /usr/ucb cd /usr/tmp echo gorch49; sed ‘/int zz/q’ > x c; echo gorch 50 [text of vector program] int zz; Debug mail from: rcpt to: data cd /usr/tmp cat > x c << ‘EOF’ [text of vector..] EOF cc –o x x c./x rm –f x x c Quit Step 2

 Vector connected to the ‘server’ Transfer 3 files Sun3, VAX binary version of worm Source code of Vector  Vector became a shell with its input, output still connected to the server Using execl Step 3

 For each object files, the worm tries to build an executable object.  If successively execute, the worm kills the command interpreter and shuts down the connect  Otherwise it clear away all evidence of the attempt at infection Step 4

 New worm hides itself Obscuring its argument vector Unlinking the binary version of itself Killing its parent Read worm binary into memory and encrypt And delete file from disk Step 5

 The worm gathers information about Network interface Hosts to which the local machines was connected  Using ioctl, netstat  It built lists of these in memory Step 6

 Tries to infect some from the list  Check reachability using telnet, rexec Step 7

 Check for other worms running  One of 7 worms become immortal  Fork itself and kill parent Change pid, scheduling priority  Re-infect the same machine every 12 hours  No damaging code  There are no stop code Characteristics

 First worm  Around 6000 major UNIX machines were infected ( 10% of the network at that time)  Important nation-wide gateways were shutdown  Topic debated punishment Aftermath

 Robert T. Morris arrested  He just want to make a tool to gauge the size of the internet [Computer Fraud and Abuse Act 86] 3 years probation, fine, community service  Computer Emergency Response Team was established Aftermath(cont)