This project is created for Hacktoberfest, showcasing common security vulnerabilities like SQL injection. The purpose is to educate and create awareness among developers about the potential risks of insecure coding practices.
A month-long celebration from October 1st - 31st to get people involved in Open Source.
Your PR must be created between October 1 and October 31 (in any time zone, UTC-12 thru UTC+14).
Your PR must be made to a public, unarchived repository.
The project demonstrates a vulnerable Flask web application that is susceptible to SQL injection attacks. It is designed for educational purposes only and should not be used in production environments. Developers can use this project to understand how SQL injection works and learn about best practices for securing web applications.
- Vulnerable Flask web application
- Simulated SQL injection attack scenarios
- Educational resources and documentation on preventing SQL injection
- Fork this repo (button on top)
- Clone on your local machine
git clone https://github.com/Google-DSC-DMCE/Vulnerable-Flask-App.git
- Navigate to project directory.
cd Vulnerable-Flask-App
- Create a new Branch
git checkout -b my-new-branchgit add .- Commit your changes.
git commit -m "Relevant message"- Then push
git push origin my-new-branch- Create a new pull request from your forked repository
- Install Flask
pip install -r requirements.txt- Run the Flask application.
python main.py- Access the application in your web browser at 'http://localhost:5000'
An easy way to avoid conflicts is to add an 'upstream' for your git repo, as other PR's may be merged while you're working on your branch/fork.
git remote add upstream https://github.com/Google-DSC-DMCE/Vulnerable-Flask-App
You can verify that the new remote has been added by typing
git remote -v
To pull any new changes from your parent repo simply run
git merge upstream/master
This will give you any eventual conflicts and allow you to easily solve them in your repo. It's a good idea to use it frequently in between your own commits to make sure that your repo is up to date with its parent.
For more information on syncing forks read this article from Github.
If you have any questions or suggestions regarding the project, feel free to contact us at sharodubey1312@gmail.com.