Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade cryptography from 2.3.1 to 42.0.0 #177

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Fab-T
Copy link

@Fab-T Fab-T commented Jan 27, 2024

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:
    • test/requirements.txt
⚠️ Warning
hca 6.3.0 has requirement cryptography==2.3.1, but you have cryptography 42.0.1.
google-auth-oauthlib 1.2.0 has requirement google-auth>=2.15.0, but you have google-auth 1.35.0.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.
boto3 1.33.13 has requirement s3transfer<0.9.0,>=0.8.2, but you have s3transfer 0.2.1.
awscli 1.31.13 has requirement s3transfer<0.9.0,>=0.8.0, but you have s3transfer 0.2.1.
awscli 1.31.13 has requirement docutils<0.17,>=0.10, but you have docutils 0.20.1.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-CRYPTOGRAPHY-6050294
cryptography:
2.3.1 -> 42.0.0
No No Known Exploit
medium severity 616/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.9
Information Exposure
SNYK-PYTHON-CRYPTOGRAPHY-6126975
cryptography:
2.3.1 -> 42.0.0
No Proof of Concept

(*) 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)

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