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
```
pyOpenSSL 20.0.1 has requirement cryptography>=3.2, but you have cryptography 3.0.
pipenv 2021.5.29 has requirement pip>=18.0, but you have pip 9.0.3.
ipdbplugin 1.5.0 requires ipython, which is not installed.
django-tablib 3.2 requires tablib, which is not installed.
django-braces 1.14.0 has requirement Django>=1.11.0, but you have Django 1.6.5.
```
Vulnerabilities that will be fixed
By pinning:
Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity
603/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 4.2
(*) 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
``` pyOpenSSL 20.0.1 has requirement cryptography>=3.2, but you have cryptography 3.0. pipenv 2021.5.29 has requirement pip>=18.0, but you have pip 9.0.3. ipdbplugin 1.5.0 requires ipython, which is not installed. django-tablib 3.2 requires tablib, which is not installed. django-braces 1.14.0 has requirement Django>=1.11.0, but you have Django 1.6.5. ```Vulnerabilities that will be fixed
By pinning:
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 4.2
SNYK-PYTHON-IPYTHON-3318382
ipython:5.10.0 -> 8.10.0(*) 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:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.
This change is