Skip to content

Latest commit

 

History

History
146 lines (87 loc) · 5.95 KB

README.md

File metadata and controls

146 lines (87 loc) · 5.95 KB
Raw

Cybersecurity Project 1

IMPORTANT

I forgot to add this in the essay, the users are:

  • user1:password1
  • user2:password2

This project has been created for the Cybersecurity MOOC Project I. The webpage will be similar to one exercise done during the Securing Software course where we had a webpage with quizzes and topics.

This project has intended security flaws but the fixes will be provided.

Security flaws

The security flaws that this project has are chosen from the OWASP 2021 Top 10 List, except for Cross-Site Request Forgery (CSRF) which is not included in the list but is a fundamental flaw in web applications.

SQL Injection

A03:2021-Injection - SQL Injection is a vulnerability that allows an attacker to execute SQL code in the server. This can be fixed by using parameterized queries.

I have made this flaw by hardcoding a SQL query in the code in the Quiz Edit, since with Django the default is sqlite and it doesn't allow to execute multiple queries at once it is not possible to drop the database, but for example it is possible to type ivan' WHERE id = 1 or 1=1 -- and now all the quizzes will have the name ivan.

This can be fixed by using parameterized queries as the code commented below the query is.

Broken Access Control

A01:2021-Broken Access Control - Broken Access Control is a vulnerability that allows an attacker to access resources that they should not have access to. This can be fixed by implementing proper access control.

To make this flaw I have removed the @login_required decorator from the QuizDeleteView and also removed the owner check, this allows anyone to delete any quiz by going to the url /quiz/<id>/delete. For the sake of testing this I added to the main quiz list the IDs and the owner of the quiz, in a real scenario this would not be the case.

Server-Side Request Forgery

A10:2021-Server-Side Request Forgery - Server-Side Request Forgery is a vulnerability that allows an attacker to make requests from the server. This can be fixed by validating the requests.

To recreate this flaw, I added a URL parameter in the Quiz Detail View, this means that if you go to /quiz/<id>?url=<url> it will make a request to that URL and return the response, this can be used to make requests to internal services that are not supposed to be exposed to the internet. http://localhost:8000/quiz/1/?url=https://jsonplaceholder.typicode.com/posts/1 is an example of this or http://localhost:8000/quiz/1/?url=http://localhost:8000/passwords/, the proper usage would be something like http://localhost:8000/quiz/1/?url=http://localhost:8000/details/1, so to fix this flaw we would have to validate the URL and make sure it is only accessing what it is supposed to access.

Security Misconfiguration

A05:2021-Security Misconfiguration - Security Misconfiguration is a vulnerability that allows an attacker to exploit a misconfiguration in the server, in a Django project this could be for example the debug mode to true, since if we then enter a URL that doesn't exist we will leak all the URLs in the project, such as the /passwords/ one (implemented only for testing SSRF).

Another potential misconfiguration is setting a weak secret key or storing it in a env file that is not in the .gitignore, this would allow an attacker to impersonate the server.

Lastly another misconfiguration could be not setting the allowed hosts, this would allow an attacker to make requests to the server from any domain, which could be used to make HTTP host header attacks.

All of these can be fixed by taking some time to configure the server properly.

Cross-Site Request Forgery

Cross-Site Request Forgery - Cross-Site Request Forgery is a vulnerability that allows an attacker to make requests like if he was the user. This can be fixed by using CSRF tokens.

To implement this flaw I simply commented out the {% csrf_token %} in the question_add.html and added the @csrf_exempt decorator in the QuestionCreateView, this allows an attacker to make requests like if he was the user.

To test it out I created a new page called CSRF Demo which is only visible if you are logged in and there is a button that will make a POST request to the QuestionCreateView and create it in one of the quizzes, this attack would be usually done with a hidden iframe or an image, but the button is easier to test and the goals is to learn about the flaws and how to fix them.

Installation

  1. Ensure you have Python installed.

  2. Clone this repository:

    git clone https://github.com/LittleHaku/cybersecurity-proj1

  3. Enter the directory:

    cd cybersecurity-proj1

  4. Install the dependencies:

    pip install -r requirements.txt

  5. Enter the directory:

    cd project

  6. Populate the database

    make populate

    If this fails, reset the database and try again.

    make resetdb

  7. Run the server:

    make run

  8. Optional: Create a superuser:

    make superuser

Other commands

Reset the database:

make resetdb

Create a superuser:

make superuser

Delete all migrations:

make delete_migrations

Migrate:

make migrate

Drop the database:

make dropdb

Funcionalities

This website allows the users to register and login, when a user is logged in he can access his quizzes by going to the Edit Quizzes tab, there he can create new ones, modify the existing ones or delete them, right now empty quizzes and empty questions are allowed, the purpose is to learn about cybersecurity so I'd rather focus on the security flaws than the functionality of the website.

As with the example seen in the course one could fail a question, go back and change the answer, I fixed it but I didn't consider it a flaw of the OWASP Top 10 List since it is not a security flaw, but more a design one.

The users can see all the quizzes from the home/main page, there they can click on one and play it.