Vulpy is a web application developed in Python / Flask / SQLite that has two faces.
GOOD: Tries to code with secure development best practices in mind.
BAD: Tries to code like (possibly) you. :p
Is developed has a laboratory for the following courses:
Secure Development of Securetia (https://www.securetia.com/cursos.html) Secure Development of EducaciónIT (https://www.educacionit.com/curso-de-desarrollo-seguro)
But you can use it has you want (MIT License)
The "GOOD" version (not finished yet) will comply with the OWASP ASVS:
https://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project
This will permit learn how to develop python code following the best security practices.
git clone https://github.com/fportantier/vulpy cd vulpy pip3 install --user -r requirements.txt
- Login/Logout
- Read posts from other users
- Publish posts
- Multi-Factor Authentication (MFA)
- API for read and write posts
- Content Security Policy
- SSL/TLS Server
Some of the vulnerabilities present on the "BAD" version:
- Cross-Site Scripting (XSS)
- SQL Injection
- Cross Site Request Forgery (CSRF)
- Session Impersonation
- Insecure Deserialization
- Authentication Bruteforce
- Authentication Bypass
Note: The "GOOD" version (not finished yet) is supposed to don't have vulnerabilities, but I'm a human being, so...
Both, "BAD" and "GOOD" versions, requires an initialization of the database.
This is done with the script "db_init.py" inside each of the directories (bad, and good).
Each version has their own sqlite files for the users and posts.
The execution of the script is, for example:
cd bad ./db_init.py
After database initialization, three users are created:
Username Password -------- ----------- admin SuperSecret elliot 123123123 tim 12345678
You can login with any user, the application doesn't have a permissions system, so, the three have the same permissions.
