Abstract: Current technologicaladvances, especially in the field of information technology have changed theorganization, but always there is risk and threat.
Computer worm is one of thevery serious threat, because it has the ability to spread very quickly in ashort time and has great damage. The purpose of this paper is to investigateand measure the metrics size of computer worm. With help of measurementapplication, such as Imagix 4D, we want to know what exactly the size of thisnasty code and how they work.
This paper measure computer worm code, withexperiments using Morris Worm code.Keywords: ComputerWorm, Magix 4D, Code, Morris Worm I. IntroductionCurrent technological advances,especially in the field of information technology have changed the organizationin carrying out its duties from day to day. The dependence of a systemconnected to each other is getting bigger.
Nevertheless, the threat of anattack on the system is running larger 1. One of the many threats that exist in anorganization to an interdependent system is the attack of a worm computer. Computerworm is one of the very serious threat, because it has the ability to spreadvery quickly in a short time and has great damage.
Computer worms work in a wayspread through the network 2, by exploiting the weaknesses of the running system. The firstworm computer, appeared in 1988, known as the Morris Worm 3. At that time its presence gained the attention of many parties.From the existing literature 4, measurement of applications is usually done on non destructiveapplications, while the measurement of destructive applications, such as worms,so far not exist.The purpose ofthis paper is to investigate the size of the, Morris Worm code, including thesize of the file, the number of code each line, the dependency between classes,and the mapping of each module.
This measurement will use Morris Worm sourcecode as sample, and using the Imagix 4D application as a measuring tools.Imagix 4D is an application to perform complete source code analysis. II.
Relatedwork in the literatureThe definition ofmeasurement according to ISO/IEC 15939 5 is set of operations having the object ofdetermining a value of a measure. To measure the size of an application’smetrics, it can use some of the tools available 6,7. One application that can be used to performsoftware metrics measurement is Imagix 4D 8. The ability of Imagix 4D is its ability to display flow charts, flowgraphs, class diagrams, metrics, and some dynamic visuals 9. Imagix 4D analysis results are capableof displaying metrics, one of which is McCabe Cyclomatic Complexity 10, which facilitates the analysis of sourcecode. III. Imagix 4d Software MetricMeasurement ExperimentsThis experiment measures the Morris Wormsource code written in C language programming. Experiments are done using theWindows 7 operating system and using Imagix 4D version 9.
0.2 (32bit). All ofthese source code will be measured using Imagix 4D, according to themeasurement sequence, the measurementsteps are as follows:1. Source code Morris Wormdownloaded from : https://github.
com/arialdomartini/morris-worm.git2. Imagix 4D application,obtained by downloading from: http://www.imagix.com3.
Installingthe Imagix 4D application, then create a new project by: “File -> NewProject …”4. Open the worm sourcecode, by: “Project -> Data Sources”5. There will be pop up window for browse and selectthe source code. After the aplication loading source code, the result will be shown.
The results of the experiment will bedescribed as follows:A. File Structure Metrics Figure 1 show Morris Worm source code, consists of 8 files,from directory named “morris-worm-master”. Each files namely:cracksome.c, hs.
c, net.c, stubs.c, worm.c, worm.
h, wormdes.c and x8113550.c. Fig. 1.
File StructureMoreover, analysis result of file metrics for each files of source code canbe see in figure 2 below : Fig. 2. File Metrics Line in file is the number oflines contained in the source code. Lines of source code is a line containingthe codes of the Morris Worm. Number of statements is the number of commandscontained in the Morris Worm. Cyclomatic Complexity10 is a lot of metrics that calculate the levelof difficulty in the source code. Average Cyclomatic Complexity is the averagedifficulty level in source code.
Max Cyclomatic Complexity is the highestdifficulty level. File size Bytes is a file size in Bytes. From Figure 2, it can be seen that the hs.c filehas the greatest difficulty level, while worm.
c has the lowest difficultylevel. B. ClassMetrics Figure 3 show Morris Wormsource code class metrics.
There are 16 classes in Morris Worm, where each theclass has its own members. Class bar has members = 1, class usr har members =10, meanwhile hst has members = 15. Others class has no members. Fig. 3. Class MetricsC. FunctionMetrics Figure 4 show Morris Wormsource code function metrics. Fig.
4. Function Metric IV. ConclusionA.
Morris Worm, like any other aplication, has sizesattached to the code inside.B. When compared with worms that are more”modern”, Morris Worm size relatively small.