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.20.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 1.26.6.
praw 6.0.0 requires update-checker, which is not installed.
gitdb2 4.0.2 requires gitdb, which is not installed.
```
(*) 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.
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.20.0 has requirement urllib3<1.25,>=1.21.1, but you have urllib3 1.26.6. praw 6.0.0 requires update-checker, which is not installed. gitdb2 4.0.2 requires gitdb, which is not installed. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 3.1
SNYK-PYTHON-DJANGO-1066259
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 3.3
SNYK-PYTHON-DJANGO-1279042
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-1290072
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-DJANGO-1298665
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 5.9
SNYK-PYTHON-DJANGO-173679
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 2.4
SNYK-PYTHON-DJANGO-174885
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-451300
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456540
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456541
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456542
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-DJANGO-456566
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 6.3
SNYK-PYTHON-DJANGO-536439
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 5.9
SNYK-PYTHON-DJANGO-72562
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 4.3
SNYK-PYTHON-DJANGO-72888
django:
2.1 -> 2.2.18
Why? Has a fix available, CVSS 9.8
SNYK-PYTHON-REQUESTS-72435
requests:
2.19.1 -> 2.20
Why? Has a fix available, CVSS 7.7
SNYK-PYTHON-URLLIB3-1014645
urllib3:
1.23 -> 1.25.9
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-URLLIB3-1533435
urllib3:
1.23 -> 1.25.9
Why? Mature exploit, Has a fix available, CVSS 7.3
SNYK-PYTHON-URLLIB3-174323
urllib3:
1.23 -> 1.25.9
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-URLLIB3-174464
urllib3:
1.23 -> 1.25.9
(*) 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