sleepytaco / UnTube

A simple, comprehensive YouTube playlist manager web app powered by YouTube Data API V3. Built with ❤ using Django, htmx and Bootstrap.
51 stars 3 forks source link

[Snyk] Security upgrade django from 3.2.6 to 3.2.13 #9

Closed snyk-bot closed 2 years ago

snyk-bot commented 2 years ago

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 ``` python3-openid 3.2.0 has requirement defusedxml<=0.4.1, but you have defusedxml 0.7.1. python-jose 3.2.0 requires rsa, which is not installed. google-auth 1.30.1 requires rsa, which is not installed. google-api-core 1.28.0 requires googleapis-common-protos, which is not installed. django-sekizai 2.0.0 requires django, which is not installed. django-polymorphic 3.0.0 requires Django, which is not installed. django-filer 2.0.2 requires django, which is not installed. django-filer 2.0.2 requires django-mptt, which is not installed. django-filer 2.0.2 requires easy-thumbnails, which is not installed. django-cms 3.8.0 requires Django, which is not installed. django-cms 3.8.0 requires django-formtools, which is not installed. django-cms 3.8.0 requires django-treebeard, which is not installed. django-classy-tags 2.0.0 requires django, which is not installed. django-appconf 1.0.4 requires django, which is not installed. django-allauth 0.44.0 requires pyjwt, which is not installed. django-allauth 0.44.0 requires Django, which is not installed. ```

Vulnerabilities that will be fixed

By pinning:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity
high severity 696/1000
Why? Recently disclosed, Has a fix available, CVSS 8.2
SQL Injection
SNYK-PYTHON-DJANGO-2606966
django:
3.2.6 -> 3.2.13
No No Known Exploit
high severity 696/1000
Why? Recently disclosed, Has a fix available, CVSS 8.2
SQL Injection
SNYK-PYTHON-DJANGO-2606969
django:
3.2.6 -> 3.2.13
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


Learn how to fix vulnerabilities with free interactive lessons:

🦉 SQL Injection 🦉 SQL Injection