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
```
requests 2.22.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5.
dcplib 3.3.0 has requirement cryptography<3,>=2.3, but you have cryptography 3.2.
cryptography 3.2 requires cffi, which is not installed.
botocore 1.12.222 has requirement urllib3<1.26,>=1.20; python_version >= "3.4", but you have urllib3 1.26.5.
```
(*) 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.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
⚠️ Warning
``` requests 2.22.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5. dcplib 3.3.0 has requirement cryptography<3,>=2.3, but you have cryptography 3.2. cryptography 3.2 requires cffi, which is not installed. botocore 1.12.222 has requirement urllib3<1.26,>=1.20; python_version >= "3.4", but you have urllib3 1.26.5. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-CRYPTOGRAPHY-1022152
cryptography:2.7 -> 3.2Why? Proof of Concept exploit, Has a fix available, CVSS 7.4
SNYK-PYTHON-PYJWT-2840625
pyjwt:1.7.1 -> 2.4.0Why? Has a fix available, CVSS 7.7
SNYK-PYTHON-URLLIB3-1014645
urllib3:1.25.8 -> 1.26.5Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-URLLIB3-1533435
urllib3:1.25.8 -> 1.26.5(*) 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 🦉 Regular Expression Denial of Service (ReDoS)