Skip to content

[Snyk] Fix for 3 vulnerabilities#267

Open
MaxMood96 wants to merge 1 commit into
masterfrom
snyk-fix-894a3c0a32703c0f45db94dcc1e542d2
Open

[Snyk] Fix for 3 vulnerabilities#267
MaxMood96 wants to merge 1 commit into
masterfrom
snyk-fix-894a3c0a32703c0f45db94dcc1e542d2

Conversation

@MaxMood96
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • requirements_all_ds.txt
⚠️ Warning
snowflake-connector-python 2.3.4 has requirement urllib3<1.26.0,>=1.20, but you have urllib3 2.0.7.
snowflake-connector-python 2.3.4 has requirement pytz<2021.0, but you have pytz 2025.2.
snowflake-connector-python 2.3.4 has requirement certifi<2021.0.0, but you have certifi 2026.1.4.
snowflake-connector-python 2.3.4 has requirement requests<2.24.0, but you have requests 2.31.0.
snowflake-connector-python 2.3.4 has requirement boto3<1.16,>=1.4.4, but you have boto3 1.33.13.
s3transfer 0.8.2 has requirement botocore<2.0a.0,>=1.33.2, but you have botocore 1.18.0.
pyOpenSSL 20.0.1 has requirement cryptography>=3.2, but you have cryptography 2.9.2.
pyathena 2.25.2 has requirement botocore>=1.29.4, but you have botocore 1.18.0.
memsql 3.0.0 requires mysqlclient, which is not installed.
impyla 0.16.0 requires thriftpy2, which is not installed.
httplib2 0.31.2 has requirement pyparsing<4,>=3.1, but you have pyparsing 2.1.4.
botocore 1.18.0 has requirement urllib3<1.26,>=1.20; python_version != "3.4", but you have urllib3 2.0.7.
boto3 1.33.13 has requirement botocore<1.34.0,>=1.33.13, but you have botocore 1.18.0.

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • 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.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Deserialization of Untrusted Data
🦉 Allocation of Resources Without Limits or Throttling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants