[Snyk] Security upgrade cryptography from 2.9.2 to 42.0.2

[chr0m1ng]

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_all_ds.txt

⚠️ Warning

snowflake-connector-python 2.1.3 has requirement requests<2.23.0, but you have requests 2.31.0.
snowflake-connector-python 2.1.3 has requirement urllib3<1.26.0,>=1.20, but you have urllib3 2.0.7.
snowflake-connector-python 2.1.3 has requirement certifi<2021.0.0, but you have certifi 2023.11.17.
snowflake-connector-python 2.1.3 has requirement pytz<2021.0, but you have pytz 2023.4.
snowflake-connector-python 2.1.3 has requirement cryptography<3.0.0,>=1.8.2, but you have cryptography 42.0.2.
pyathena 2.25.2 has requirement boto3>=1.26.4, but you have boto3 1.10.50.
pyathena 2.25.2 has requirement botocore>=1.29.4, but you have botocore 1.13.50.
memsql 3.0.0 requires mysqlclient, which is not installed.
impyla 0.16.0 requires thriftpy2, which is not installed.
httplib2 0.22.0 has requirement pyparsing!=3.0.0,!=3.0.1,!=3.0.2,!=3.0.3,<4,>=2.4.2; python_version > "3.0", but you have pyparsing 2.1.4.
dql 0.5.26 has requirement python-dateutil<2.7.0, but you have python-dateutil 2.8.2.
botocore 1.13.50 has requirement urllib3<1.26,>=1.20; python_version >= "3.4", but you have urllib3 2.0.7.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	451/1000 Why? Recently disclosed, Has a fix available, CVSS 3.3	NULL Pointer Dereference SNYK-PYTHON-CRYPTOGRAPHY-6210214	cryptography: 2.9.2 -> 42.0.2	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:

🦉 NULL Pointer Dereference