Skip to content
This repository has been archived by the owner on May 19, 2021. It is now read-only.

[Snyk] Security upgrade cryptography from 2.2.2 to 3.3.2 #31

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

Conversation

jank
Copy link
Member

@jank jank commented Feb 9, 2021

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
⚠️ Warning
cryptography 3.3.2 has requirement cffi>=1.12, but you have cffi 1.11.5.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 581/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Cryptographic Issues
SNYK-PYTHON-CRYPTOGRAPHY-1070544
cryptography:
2.2.2 -> 3.3.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 effected 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

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

Coverage Status

Coverage remained the same at 100.0% when pulling daeb4d6 on snyk-fix-f83d924d69e75e907c3aaec5c076ffef into 1b08298 on master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants