Project 2: WebFall 2020

This project counts for 13% of your course grade. Late submissions will be penalized by 10% of the maximum attainable score, plus an additional 10% every 4 hours until received. Late work will not be accepted after the start of the next lab (of any section) following the day of the deadline. If you have a conflict due to travel, interviews, etc., please plan accordingly and turn in your project early.

The code and other answers you submit must be entirely your own work, and you are bound by the Honor Code. You may discuss the conceptualization of the project and the meaning of the questions, but you may not look at any part of someone else’s solution or collaborate with anyone. You may consult published references, provided that you appropriately cite them (e.g., with program comments). Visit the course website for the full collaboration policy.

Solutions must be submitted electronically to GitHub and Gradescope per the submission checklist below.


In this project, we provide an insecure website, and your job is to attack it by exploiting three common classes of vulnerabilities: SQL injection, cross-site scripting (XSS), and cross-site request forgery (CSRF). You are also asked to exploit various flawed defenses meant to prevent these attacks. Understanding how these attacks work will help you better defend your own web applications.


  • Learn to spot common vulnerabilities in websites and to avoid them in your own projects.
  • Understand the risks these problems pose and the weaknesses of naive defenses.
  • Gain experience with web architecture and with HTML, JavaScript, and SQL programming.

Read this First

This project asks you to develop attacks and test them, with our permission, against a target website that we are providing for this purpose. Attempting the same kinds of attacks against other websites without authorization is prohibited by law and university policies and may result in fines, expulsion, and jail time. You must not attack any website without authorization! Per the course ethics policy, you are required to respect the privacy and property rights of others at all times, or else you will fail the course. See the “Ethics, Law, and University Policies” section on the homepage for more info.

Target Website

A startup named BUNGLE! is about to launch its first product—a web search engine—but their investors are nervous about security problems. Unlike the Bunglers who developed the site, you took EECS 388, so the investors have hired you to perform a security evaluation before it goes live.

BUNGLE! is available for you to test at For security reasons, the site is only accessible when using the version of Firefox provided in the Common VM.

Update: The version of Firefox preinstalled on the common VM is unusable. Please follow the instructions in the browser guidelines section to download a working version onto your VM.

The site is written in Python using the Bottle web framework. Although Bottle has built-in mechanisms that help guard against some common vulnerabilities, the Bunglers have circumvented or ignored these mechanisms in several places. If you wish, you can inspect the Python source code, but this is not necessary to complete the project.

In addition to providing search results, the site accepts logins and tracks users’ search histories. It stores usernames, passwords, and search history in a MySQL database.

Passwords used on BUNGLE! may be exposed to others. Never use an important password to test an insecure site! This especially includes your personal passwords.

Before being granted access to the source code, you reverse engineered the site and determined that it replies to five main URLs: /, /search, /login, /logout, and /create. The function of these URLs is explained below, but if you want an additional challenge, you can skip the rest of this section and do the reverse engineering yourself.

  • Main page (/)

    The main page accepts GET requests and displays a search form. When submitted, this form issues a GET request to /search, sending the search string as the parameter “q”.

    If no user is logged in, the main page also displays a form that gives the user the option of logging in or creating an account. The form issues POST requests to /login and /create.

  • The search results page accepts GET requests and prints the search string, supplied in the “q” query parameter, along with the search results. If the user is logged in, the page also displays the user’s recent search history in a sidebar.

    Note: Since actual search is not relevant to this project, you might not receive any results.

  • Login handler (/login)

    The login handler accepts POST requests and takes plaintext “username” and “password” query parameters. It checks the user database to see if a user with those credentials exists. If so, it sets a login cookie and redirects the browser to the main page. The cookie tracks which user is logged in; manipulating or forging it is not part of this project.

  • Logout handler (/logout)

    The logout handler accepts POST requests. It deletes the login cookie, if set, and redirects the browser to the main page.

  • Create account handler (/create)

    The create account handler accepts POST requests and receives plaintext “username” and “password” query parameters. It inserts the username and password into the database of users, unless a user with that username already exists. It then logs the user in and redirects the browser to the main page.

    Note: The password is neither sent nor stored securely; however, none of the attacks you implement should depend on this behavior. You should choose a password that others will not guess, but again, never use an important password to test an insecure site!



This project has been tested and will be graded using Firefox v78.0.0 on Linux. The common VM for projects 1-4 was designed to ship with this version of Firefox, however, we have recently observed that the bundle you will see in the eecs388p2 folder in your Desktop is corrupted. Please delete the old folder and download the tarball with the fix from this link. You can extract it with tar -xzvf eecs388p2.tar.gz.

Within the folder, run open-bungle. This opens Bungle within Firefox and configures Firefox to prevent auto-updating.

In addition, we provide this version of Firefox on the CAEN Linux machines, and it can be launched with this command: /afs/

Defense Levels

The Bunglers have been experimenting with some naïve defenses, and you need to demonstrate that these provide insufficient protection. In Parts 2 and 3, the site includes drop-down menus at the top of each page that let you change the CSRF and XSS defenses that are in use. When you are testing your solution, ensure that BUNGLE! has the correct defense levels set. You may not attempt to subvert the mechanism for changing the level of defense in your attacks. Be sure to test your solutions with the appropriate defense levels!

In all parts, you should implement the simplest attack you can think of that defeats the given set of defenses. In other words, do not simply attack the highest level of defense and submit that attack as your solution for all defenses. You do not need to combine the vulnerabilities, unless explicitly stated.

When grading, the correct defense levels will be set on Bungle before the autograder runs your solution; don't worry about setting this through your code.


The Firefox Developer Tools will be very helpful for this project, particularly the JavaScript console and debugger, DOM inspector, and network monitor. See

Although general purpose tools are permitted, you are not allowed to use tools that are designed to automatically test for vulnerabilities. Additionally, your solutions may not use any libraries other than jQuery, which has already been included on BUNGLE!.

Your solutions will involve manipulating SQL statements and writing web code using HTML, JavaScript, and the jQuery library. You should search the web for answers to basic how-to questions. There are many fine online resources for learning these tools. Here are a few that we recommend:

To learn more about SQL Injection, CSRF, and XSS attacks, and for tips on exploiting them, see:

Part 1. SQL Injection

Your first goal is to demonstrate SQL injection attacks that log you in as an arbitrary user without knowing the password. In order to protect other students’ accounts, we’ve made a series of separate login forms for you to attack that aren’t part of the main BUNGLE! site. For each of the following defenses, provide inputs to the target login form that successfully log you in as the user “victim”:

1.0 No defenses

You can assume that the password field is simply enclosed in single quotes.

Submission: sql_0.txt

1.1 Simple escaping

The server escapes single quotes (') in the inputs by replacing them with two single quotes.

Submission: sql_1.txt

1.2 Escaping and Hashing

The server uses the following PHP code, which escapes the username and applies the MD5 hash function to the password.

if (isset($_POST['username']) and isset($_POST['password'])) {
    $username = mysql_real_escape_string($_POST['username']);
    $password = md5($_POST['password'], true);
    $sql_s = "SELECT * FROM users WHERE username='$username' and pw='$password'";
    $rs = mysql_query($sql_s);
    if (mysql_num_rows($rs) > 0) {
        echo "Login successful!";
    } else {
        echo "Incorrect username or password";

This is more difficult than the previous two defenses. You will need to write a program to produce a working exploit. You can use any language you like, but we recommend Python 3.

Hint: If you are using a hex digest to see if the hash contains your target string, be very careful of where you find the string within your hash. With a hex digest, two characters correspond to one byte. Consequently, if the index is odd, the characters will not be in the correct position to be interpreted byte by byte.

Submissions: sql_2.txt and a directory called sql_2-src/

1.3 The SQL [Extra credit]

This target uses a different database. Your job is to use SQL injection to retrieve:

  • The name of the database
  • The version of the SQL server
  • All of the names of the tables in the database
  • A secret string hidden in the database

Submission: sql_3.txt

For this part, the text file you submit should start with a list of all the queries you made to learn the answers. Follow this with the values specified above, using this format:


Name: *DB name*
Version: *DB version string*
Tables: *comma separated names*
Secret: *secret string*

What to submit

For 1.0, 1.1, and 1.2, when you successfully log in as victim, the server will provide a URL-encoded string of your form inputs. Submit a text file with the specified filename containing only this string. For 1.2, also submit the source code for the program you wrote by placing it in the directory sql_2-src. For 1.3, submit a text file as specified.

Part 2. Cross-site Scripting (XSS)

Your next task is to demonstrate XSS attacks against the BUNGLE! search box, which does not properly filter search terms before echoing them to the results page. For each of the defenses below, your goal is to construct a URL that, when loaded in the victim’s browser, correctly executes the specified payload. We recommend that you begin by testing with a simple payload (e.g., alert(0);), then move on to the full payload. Note that you should be able to implement the payload once, then use different means of encoding it to bypass the different defenses.

Note: jQuery is embedded on Bungle. Please do not reload it in your scripts for Part 2.


The payload (the code that the attack tries to execute) will steal the username and the most recent search the real user has performed on the BUNGLE! site. When a victim visits the URL you create, these stolen items should be sent to the attacker’s server for collection.

For purposes of grading, your attack should report these events by loading (i.e. sending a GET request to) the following URL: http://localhost:31337/?stolen_user=username&last_search=last_search

You can test receiving this data by running this command at the shell in your project directory:

$ python3 -m http.server -b 31337

and observing the HTTP GET request that your payload generates in the server log.

For full credit, make sure your payload functions exactly as specified above. We cannot accept solutions that load an incorrect URL, use an incorrect request method, or send extraneous data.

Hint: If your XSS inject works when you type it into the console but not when you search it from Bungle, this is all about timing. Because the search history is tied to your account, Bungle may have to make another request to its backend server once the DOM loads. You will want to ensure your code is not called until everything in the DOM is ready.


There are five levels of defense. In each case, you should submit the simplest attack you can find that works against that defense; you should not simply attack the highest level and submit your solution for that level for every level. Try to use a different technique for each defense. The Python code that implements each defense is shown below, along with the target URL and the filename you should submit.

Note that the defenses are not cumulative; 2.2, for example, does not cover the sanitation done for 2.1.

2.0 No defenses

Submission: xss_0.txt

For 2.0 only, also submit a human-readable version of your payload code (as opposed to the form encoded into the URL). Save it in a file named xss_payload.html.

2.1 Remove “script”

filtered = re.sub(r"(?i)script", "", input)
Submission: xss_1.txt

2.2 Remove several tags

filtered = re.sub(r"(?i)script|<img|<body|<style|<meta|<embed|<object", "", input)
Submission: xss_2.txt

2.3 Remove some punctuation
filtered = re.sub(r"[;'\"]", "", input)

Submission: xss_3.txt

2.4 Encode < and > [Extra credit]
filtered = input.replace("<", "&lt;").replace(">", "&gt;")

Submission: xss_4.txt

This challenge is hard. We think it requires finding a 0-day vuln or a bug in our code.

What to submit

In addition to the the human-readable (non–URL-encoded) payload submitted for part 2.0, your submission will be a text file with the specified filename for each level of defense that contains a single line consisting of a URL. When this URL is loaded in a victim’s browser, it should execute a payload against the specified target. The payload encoded in your URLs may embed inline JavaScript. That is, it should include the localhost URL given earlier in this spec!

Part 3. Cross-site Request Forgery (CSRF)

Your final goal is to demonstrate CSRF vulnerabilities against the login form, and BUNGLE! has provided two variations of their implementation for you to test. Your goal is to construct attacks that surreptitiously cause the victim to log in to an account you control, thus allowing you to monitor the victim’s search queries by viewing the search history for this account. For each of the defenses below, create an HTML file that, when opened by a victim, logs their browser into BUNGLE! under the account “attacker” and password “l33th4x”.

Your solutions should not require any user action beyond simply loading the page once. That is, your code should not rely on user input. The browser should just display a blank page, with no evidence of an attack. (If the victim later visits BUNGLE!, it will say “logged in as attacker”, but that’s fine for purposes of the project. After all, most users won’t immediately notice.)

3.0 No defenses

Submission: csrf_0.html

3.1 Token validation

The server sets a cookie named csrf_token to a random 16-byte value and also includes this value as a hidden field in the login form. When the form is submitted, the server verifies that the client’s cookie matches the value in the form. You are allowed to exploit the XSS vulnerability from Part 2 to accomplish your goal.

Submission: csrf_1.html

3.2 Token validation, without XSS [Extra credit]

Accomplish the same task as in 3.1 without using XSS.

Submission: csrf_2.html

This challenge is hard. We think it requires finding a 0-day vuln or a bug in our code.

What to submit

For each part, submit an HTML file with the given name that accomplishes the specified attack against the specified target URL. The HTML files you submit may embed inline JavaScript.

Note: Since you’re sharing the attacker account with other students, we’ve hard-coded it so the search history won’t actually update. You can test with a different account you create to see the history change.

Tips and advice

In the past, students have lost credit on this part for various preventable reasons. Here are some tips on how to avoid common pitfalls:

  • Double check to make sure you use the exact target endpoints specified. Note that these endpoints use HTTPS!

  • Do not rely on JavaScript methods that force the script to sleep for a hard-coded time interval, as this approach may not work consistently across all situations.

  • When obtaining cookie data, avoid hardcoding any values beyond those given above. Search online to find general best practices for these tasks.

  • Your solution must work quickly and discreetly to evade detection. This means no automatic redirects, in any part of your HTML page or in any of its frames.

  • Apply the security mindset and test your exploit thoroughly, multiple times just to be safe! Make sure to clear any cookies and disable any extensions that may interfere.

Part 4. Writeup: Better Defenses

For each of the three kinds of attacks (SQL injection, XSS, and CSRF), write a paragraph of advice for the BUNGLE! developers about what techniques they should use to defend themselves. Keep in mind that, as a bugeoning startup, BUNGLE! is working on multiple other products, so make sure your advice is general and applies to more than just their demo website.

What to submit

Please submit your security recommendations to Gradescope.

Submission Details

  1. Create a repo using this GitHub Classroom link.

  2. GitHub Classroom will prompt you to join a team or create one.

    • If you are working alone, name the team with your uniqname appended with -p2. For example: mallory-p2

    • If you are in a partnership, name the team with both partner's uniqnames in any order with a hyphen in between and append -p2. For example: alice-bob-p2. Ensure that only one team exists (using the same example, bob-alice-p2 should not exist).

    Please follow this naming scheme in order to ensure timely grading. If your team name needs to be corrected, contact the course staff for assistance.

  3. When submitting your writeup to Gradescope, ensure that your submission is linked to the same team members as in GitHub Classroom.

  4. At the deadline, your GitHub repository will be cloned automatically for grading. If you need to submit any part of the assignment late, you must report the hash of the GitHub commit you want graded using the late submission form. The late penalty will be computed based on the timestamp of this form submission, not the timestamp of the commit, and will apply to all parts of the project.

Ensure the following items are completed and submitted by the deadline:

Part 1: SQL Injection

1.0 No defenses
1.1 Simple escaping
1.2 Escaping and Hashing
1.2 Escaping and Hashing
1.3 (Extra credit) The SQL

Part 2: XSS

2.0 No defenses
2.0 No defenses
2.1 Remove “script”
2.2 Remove several tags
2.3 Remove some punctuation
2.4 (Extra credit) Encode < and >

Part 3: CSRF

3.0 No defenses
3.1 Token validation
3.2 (Extra credit) Token validation, without XSS

Part 4: Writeup