Skip to content
This repository has been archived by the owner on Aug 21, 2022. It is now read-only.

[Snyk] Security upgrade django from 3.1.13 to 3.2.12 #143

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Feb 2, 2022

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
social-auth-app-django 4.0.0 requires social-auth-core, which is not installed.
snapshottest 0.5.1 requires fastdiff, which is not installed.
requests 2.24.0 has requirement urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1, but you have urllib3 1.26.5.
python3-openid 3.2.0 has requirement defusedxml<=0.4.1, but you have defusedxml 0.6.0.
python-jose 3.2.0 requires rsa, which is not installed.
ipdb 0.13.3 requires ipython, which is not installed.
google-auth 1.30.0 requires rsa, which is not installed.
google-auth 1.30.0 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.
google-api-core 1.26.1 has requirement setuptools>=40.3.0, but you have setuptools 39.0.1.
factory-boy 2.12.0 requires Faker, which is not installed.
drf-jwt 1.19.0 requires PyJWT, which is not installed.
django-model-utils 4.0.0 has requirement Django>=2.0.1, but you have Django 1.11.29.

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
medium severity 496/1000
Why? Recently disclosed, Has a fix available, CVSS 4.2
Cross-site Scripting (XSS)
SNYK-PYTHON-DJANGO-2389002
django:
3.1.13 -> 3.2.12
No No Known Exploit
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-PYTHON-DJANGO-2389021
django:
3.1.13 -> 3.2.12
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


This change is Reviewable

@gitpod-io
Copy link

gitpod-io bot commented Feb 2, 2022

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.

1 participant