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 39.0.1 to 42.0.2 #1727

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

Conversation

tberey
Copy link
Contributor

@tberey tberey commented Feb 1, 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:
    • requirements.txt

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Use of a Broken or Risky Cryptographic Algorithm
SNYK-PYTHON-CRYPTOGRAPHY-6149518
cryptography:
39.0.1 -> 42.0.2
No No Known Exploit
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-PYTHON-CRYPTOGRAPHY-6157248
cryptography:
39.0.1 -> 42.0.2
No No Known Exploit
low severity 451/1000
Why? Recently disclosed, Has a fix available, CVSS 3.3
NULL Pointer Dereference
SNYK-PYTHON-CRYPTOGRAPHY-6210214
cryptography:
39.0.1 -> 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:

🦉 Use of a Broken or Risky Cryptographic Algorithm
🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')
🦉 NULL Pointer Dereference

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