!	Assignment #4

Type of assignment: This assignment should be done in same groups as the term project.

Note: The assignment submission should clearly list the student members of the group, their names, and student numbers on the first page.

Points: The maximum number of points for this assignment is 45, which will be prorated accordingly after all assignments are posted. Weight of each problem is in parenthesis.

Format:

Assignment submissions are accepted in the following formats only: PDF (.pdf). Assignments submitted in any other format will be discarded. All text in the assignment submissions must be typed and figures plotted to be easy to read and understand. Spelling, grammar, and other language errors will result in fewer points credited to the corresponding problem solutions.
Your submission file should be named to reflect the group number (see group number assignments below), and the assignment number, e.g., group53-5.pdf.

Problems

(10) (Malicious Logic): Pick one of the following malicious software (malware):
1. Post a message (one message per group) in the course piazza indicating which malware your group has picked.
2. If another group posted an earlier message indicating that they had picked the same malware as your group, go back to step 1 and pick "free" malware.
3. Analyze the design of the picked malware, i.e., its structure, behavior, mechanisms it uses for selecting victims, infecting them, hiding itself and its authors, etc.
4. Identify the aspects specific to your malware that can be used to detect or prevent it. Based on your analysis, recommend short, medium and log term countermeasures (i.e., protection and detection techniques) against the threat posed by this malware. Classify your techniques using material from the corresponding course session.
5. Identify which of the principles for designing secure systems have not been followed by the developers of those systems vulnerabilities in which allowed the malware you analyzed to become effective.
6. Cite all your sources of information.
7. Use no more than 4 pages to write a short report documenting your findings obtained in steps 3--5. Use figures and tables, if necessary to achieve better impact of your report.
8. Your report should be submitted as one file in format of IEEE Transactions with proper title, authors, abstract, introduction, body, conclusion, and references sections.
9. Post your report in PDF on piazza by the same deadline as the one for this assignment. Marks for late reports will be decreased, 1% of the problem mark per each minute after the deadline.

(35) (Development of Secure Software): Each group is to complete successfully as many lessons as it can by logging in http://webgoat.ece.ubc.ca/WebGoat/attack (you have to be on UBC network to be able access it, if working form home vpn to ubc with your CWL account) with the corresponding user name and password from the following table. Groups cannot help each other. If it is found out that one group received help from another group, both groups will receive zero points for this problem even if one of them is eligible for the bonus points (see below). Half a point per completed lesson will be credited for this problem. Not all questions are equally difficult. The lessons are on learning about common vulnerabilities of Web applications. Some of these vulnerabilities are common to many other types of software applications.

Important rule: you must not examine the source code of WebGoat distribution in order to help yourself with the assignment.

Hints for increasing success with this problem:

You can access webgoat.ece.ubc.ca only from the UBC network. To access it from outside of the UBC network, you need to use VPN (see www.vpn.ubc.ca for instructions). If on campus, use an IAPv2 port, which can be found in various buildings, including MacLeod and the Libraries. Direct your questions about IAPv2 port to ECE IT services (help@ece.ubc.ca).
Install personal copy of WebGoat on your computer(s) so that you restart WebGoat whenever it crashes because of your actions. webgoat.ece.ubc.ca will crash too often if each group will be trying to attack it while doing this assignment.
If you cannot access webgoat.ece.ubc.ca because, for example, your or another group crashed WebGoat, send e-mail asking to reboot WebGoat on webgoat.ece.ubc.ca to help@ece.ubc.ca. The course teaching staff does not have privileges to reboot WebGoat on that host.

Attention: Only the report card on webgoat.ece.ubc.ca is what counts for marks. So, make sure your group account completes the lessons on webgoat.ece.ubc.ca.

username

password
group1
m1Gj8Orw
group2
dGcU8p12
group3
B4rZXiSq
group4
vt3N0AZ5
group5
dp6kqZnr
group6
6qR21zD8
group7
7YsCLwyL
group8
LfQA4C8t
group9
Ae27wlAD
group10
Mi8WmsCj
group11
TTuDnYC8
group12
xAdDVsa9
group13
fB4gsRSv
group14
lxDvV4u2
group15
ObYq7OD1
group16
xnw8A8qe
group17
8r67eNHA
group18
S8DKCx9e
group19
 
group20
 
group21
 
group22
 
group23
 
group24
 
group25
 

(9 points) (Bonus question) First group who can also complete the challenge of attacking three "hackable" admin interfaces and post a message on piazza indicating that it completed the challenge will receive additional (i.e., bonus) 9 points for this assignment. The group will have to demonstrate to the course TA the technique of accomplishing the challenge before the credit will be dispensed. If the group fails to demonstrate, the second group will become eligible for the bonus.

Important rule: you must not examine the source code of WebGoat distribution in order to help yourself with the assignment.

Assignment #4

Problems