[Snyk] Fix for 22 vulnerabilities

[Dala0]

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.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

Changes included in this PR

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

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	509/1000 Why? Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3172287	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	454/1000 Why? Has a fix available, CVSS 4.8	Expected Behavior Violation SNYK-PYTHON-CRYPTOGRAPHY-3314966	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	616/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.9	Use After Free SNYK-PYTHON-CRYPTOGRAPHY-3315324	cryptography: 3.3.2 -> 41.0.3	No	Proof of Concept
	584/1000 Why? Has a fix available, CVSS 7.4	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-PYTHON-CRYPTOGRAPHY-3315328	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Timing Attack SNYK-PYTHON-CRYPTOGRAPHY-3315331	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315452	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315972	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315975	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3316038	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3316211	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5663682	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	691/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.4	Improper Certificate Validation SNYK-PYTHON-CRYPTOGRAPHY-5777683	cryptography: 3.3.2 -> 41.0.3	No	Proof of Concept
	399/1000 Why? Has a fix available, CVSS 3.7	Insufficient Verification of Data Authenticity SNYK-PYTHON-CRYPTOGRAPHY-5813745	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813746	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	399/1000 Why? Has a fix available, CVSS 3.7	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813750	cryptography: 3.3.2 -> 41.0.3	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Denial of Service (DoS) SNYK-PYTHON-DJANGO-3039675	django: 3.2.15 -> 3.2.21	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-DJANGO-3266406	django: 3.2.15 -> 3.2.21	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-DJANGO-3319450	django: 3.2.15 -> 3.2.21	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Arbitrary File Upload SNYK-PYTHON-DJANGO-5496950	django: 3.2.15 -> 3.2.21	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-DJANGO-5750790	django: 3.2.15 -> 3.2.21	No	No Known Exploit
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-DJANGO-5880505	django: 3.2.15 -> 3.2.21	No	No Known Exploit
	519/1000 Why? Has a fix available, CVSS 6.1	Information Exposure SNYK-PYTHON-REQUESTS-5595532	requests: 2.25.1 -> 2.31.0	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:

🦉 Use After Free
🦉 Access of Resource Using Incompatible Type ('Type Confusion')
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn

[github-actions]

This was published to a Docker image at AWS_ACCOUNT_ID.dkr.ecr.AWS_REGION.amazonaws.com/pluto-user-beacon:113

[richpryce]

👍