[Snyk] Security upgrade cryptography from 3.3.2 to 39.0.1

[stevemac007]

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

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 -> 39.0.1	No	No Known Exploit
	526/1000 Why? Recently disclosed, Has a fix available, CVSS 4.8	Expected Behavior Violation SNYK-PYTHON-CRYPTOGRAPHY-3314966	cryptography: 3.3.2 -> 39.0.1	No	No Known Exploit
	581/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	Use After Free SNYK-PYTHON-CRYPTOGRAPHY-3315324	cryptography: 3.3.2 -> 39.0.1	No	No Known Exploit
	656/1000 Why? Recently disclosed, Has a fix available, CVSS 7.4	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-PYTHON-CRYPTOGRAPHY-3315328	cryptography: 3.3.2 -> 39.0.1	No	No Known Exploit
	551/1000 Why? Recently disclosed, Has a fix available, CVSS 5.3	Timing Attack SNYK-PYTHON-CRYPTOGRAPHY-3315331	cryptography: 3.3.2 -> 39.0.1	No	No Known Exploit
	581/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315452	cryptography: 3.3.2 -> 39.0.1	No	No Known Exploit
	581/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315972	cryptography: 3.3.2 -> 39.0.1	No	No Known Exploit
	581/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-3315975	cryptography: 3.3.2 -> 39.0.1	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:

🦉 Denial of Service (DoS) 🦉 Denial of Service (DoS)