IT Security Attacking Virtual Machine Project
CSI 5480 – Information Security Practice
Project 3 (Prj3)
Connects to the following learning outcomes:
Footprinting, scanning, and enumeration; common system vulnerabilities; system remediation and
hardening; intrusion detection; hands-on experiments on information security.
December 5th, at 23:59:59 PM.
The challenge is to analyze, ethically exploit, and mitigate a stack overflow in a target executable.
Please follow the steps below to deploy the required files in your testbed and ethically develop the
1) Decompress the archive Project3.zip. The files in that archive are the following:
a) stats, an ELF 64-bit LSB executable
b) stats.txt, a text file that is used to store statistical data
c) stats.c is the source code for the stats executable
2) Place the files stats and stats.txt on the Virtual Machine under the path “/usr/ctf/museum/html/cgi-
bin”. You can use sftp to upload those files onto the Virtual Machine.
3) Run the target executable stats on the Virtual Machine, and ethically exploit it over the virtual
network from the physical machine. Figuring out the port that stats listens on is part of the footprinting
and scanning challenge, so no information is given here at this time.
Students can use the publicly available shellcode from shell storm:
The actual shellcode is the following sequence of bytes:
Do not forget to replace PORT with the two bytes that represent the port that you chose to connect to
and get a shell on the compromised machine. Once you inject the shellcode and execute it on the virtual
machine, you need to use netcat to connect to it on the port in question, and that is how you get the
The deliverable will be an exploit that interacts with the target executable stats such as to inject code
into its memory, and thus corrupt addresses such as to have the injected code executed. The injected
code should run a shell on the compromised machine.
As a mitigation, develop a SNORT rule that can detect your exploit without false positives.
1) There is a mechanism in place to protect the saved instruction pointer, i.e., the return address, from corruption.
2) The stack may not be your only friend!
Good luck to you!
The following rubric details how your submission will be graded:
Correct exploit with correct SNORT
Correct exploit but no working SNORT
Partially correct exploit with correct
Partially correct exploit with partially
correct SNORT signature.
Incorrect or no exploit. 0