Skip to content

[Snyk] Security upgrade cryptography from 45.0.5 to 46.0.5#16

Open
devRoemer wants to merge 1 commit intomasterfrom
snyk-fix-e9c4f856b328afe594a7c9b9595f5b3d
Open

[Snyk] Security upgrade cryptography from 45.0.5 to 46.0.5#16
devRoemer wants to merge 1 commit intomasterfrom
snyk-fix-e9c4f856b328afe594a7c9b9595f5b3d

Conversation

@devRoemer
Copy link
Contributor

snyk-top-banner

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

Snyk changed the following file(s):

  • requirements.txt

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-15263096
Copy link
Contributor

@cwehmeier cwehmeier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have updated the cryptography package in KIT-4716 anways. So we can close this PR without merging.

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.

3 participants