[Snyk] Security upgrade cryptography from 2.9.2 to 41.0.0

[rhiananthony]

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

requests 2.20.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 1.25.11.
hca 6.5.1 has requirement jsonschema<3,>=2.6, but you have jsonschema 4.17.3.
hca 6.5.1 has requirement dcplib<3,>=2.0.2, but you have dcplib 3.12.0.
hca 6.5.1 has requirement cryptography<3,>=2.6.1, but you have cryptography 41.0.1.
google-auth-oauthlib 1.0.0 has requirement google-auth>=2.15.0, but you have google-auth 1.35.0.
google-api-core 2.11.0 has requirement google-auth<3.0dev,>=2.14.1, but you have google-auth 1.35.0.
Flask 2.2.5 has requirement Jinja2>=3.0, but you have Jinja2 2.11.3.
dcplib 3.12.0 has requirement cryptography<3,>=2.3, but you have cryptography 41.0.1.
dcplib 3.12.0 has requirement termcolor<2,>=1.1.0, but you have termcolor 2.3.0.
botocore 1.12.208 has requirement jmespath<1.0.0,>=0.7.1, but you have jmespath 1.0.1.
boto3 1.26.145 has requirement botocore<1.30.0,>=1.29.145, but you have botocore 1.12.208.
argcomplete 1.12.3 has requirement importlib-metadata<5,>=0.23; python_version == "3.7", but you have importlib-metadata 6.6.0.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	581/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5663682	cryptography: 2.9.2 -> 41.0.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:

🦉 Denial of Service (DoS)