[Snyk] Fix for 41 vulnerabilities #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
By pinning:
SNYK-PYTHON-DJANGO-1066259
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-1076802
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-1090612
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-1279042
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-1290072
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-1298665
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-1298666
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2312875
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2329158
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2329159
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2329160
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2389002
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2389021
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2606966
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2606969
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2940618
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-2968205
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-3319450
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-536439
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-538244
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-543998
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-5496950
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-559326
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-571013
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-571014
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-5750790
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-5880505
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-609368
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-DJANGO-609369
django:
2.2.7 -> 3.2.21
SNYK-PYTHON-NUMPY-2321964
numpy:
1.17.4 -> 1.22.2
SNYK-PYTHON-NUMPY-2321966
numpy:
1.17.4 -> 1.22.2
SNYK-PYTHON-NUMPY-2321969
numpy:
1.17.4 -> 1.22.2
SNYK-PYTHON-NUMPY-2321970
numpy:
1.17.4 -> 1.22.2
SNYK-PYTHON-PYJWT-2840625
pyjwt:
1.7.1 -> 2.4.0
SNYK-PYTHON-RSA-1038401
rsa:
4.0 -> 4.7
SNYK-PYTHON-RSA-570831
rsa:
4.0 -> 4.7
SNYK-PYTHON-SCIPY-5756497
scipy:
1.5.4 -> 1.10.0rc1
SNYK-PYTHON-SCIPY-5759266
scipy:
1.5.4 -> 1.10.0rc1
SNYK-PYTHON-WERKZEUG-3319935
werkzeug:
2.0.3 -> 2.3.8
SNYK-PYTHON-WERKZEUG-3319936
werkzeug:
2.0.3 -> 2.3.8
SNYK-PYTHON-WERKZEUG-6035177
werkzeug:
2.0.3 -> 2.3.8
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:
🦉 Directory Traversal
🦉 Improper Input Validation
🦉 Access Restriction Bypass
🦉 More lessons are available in Snyk Learn