[Snyk] Fix for 6 vulnerabilities

[poteddy]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

pyOpenSSL 23.2.0 has requirement cryptography!=40.0.0,!=40.0.1,<42,>=38.0.0, but you have cryptography 35.0.0.
google-auth 2.3.2 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.
google-api-core 2.12.0 has requirement google-auth<3.0.dev0,>=2.14.1, but you have google-auth 2.3.2.
django-test-migrations 1.1.0 has requirement typing_extensions<4.0.0,>=3.7.4, but you have typing-extensions 4.7.1.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	554/1000 Why? Has a fix available, CVSS 6.8	Insufficient Verification of Data Authenticity SNYK-PYTHON-CERTIFI-3164749	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	704/1000 Why? Has a fix available, CVSS 9.8	Improper Following of a Certificate's Chain of Trust SNYK-PYTHON-CERTIFI-5805047	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	369/1000 Why? Has a fix available, CVSS 3.1	Directory Traversal SNYK-PYTHON-DJANGO-1066259	django: 1.11.29 -> 2.2.24	No	No Known Exploit
	379/1000 Why? Has a fix available, CVSS 3.3	Directory Traversal SNYK-PYTHON-DJANGO-1279042	django: 1.11.29 -> 2.2.24	No	No Known Exploit
	579/1000 Why? Has a fix available, CVSS 7.3	HTTP Header Injection SNYK-PYTHON-DJANGO-1290072	django: 1.11.29 -> 2.2.24	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Directory Traversal SNYK-PYTHON-DJANGO-1298665	django: 1.11.29 -> 2.2.24	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal