PatrowlManager [Snyk] Fix for 7 vulnerabilities

[Snyk] Fix for 7 vulnerabilities

Open MaKyOtOx opened this issue 2 years ago • 1 comments

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

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
- requirements.txt

⚠️ Warning

django-celery-beat 2.0.0 requires django-timezone-field, which is not installed.
celery 4.4.7 has requirement kombu<4.7,>=4.6.10, but you have kombu 4.6.7.
celery 4.4.7 has requirement billiard<4.0,>=3.6.3.0, but you have billiard 3.6.1.0.

Vulnerabilities that will be fixed

By pinning:

Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
651/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 6.6	Stored Command Injection SNYK-PYTHON-CELERY-2314953	`celery:` `4.4.0 -> 5.2.2`	No	Proof of Concept
424/1000 Why? Has a fix available, CVSS 4.2	Cross-site Scripting (XSS) SNYK-PYTHON-DJANGO-2389002	`django:` `2.2.26 -> 3.2.15`	No	No Known Exploit
479/1000 Why? Has a fix available, CVSS 5.3	Denial of Service (DoS) SNYK-PYTHON-DJANGO-2389021	`django:` `2.2.26 -> 3.2.15`	No	No Known Exploit
624/1000 Why? Has a fix available, CVSS 8.2	SQL Injection SNYK-PYTHON-DJANGO-2606966	`django:` `2.2.26 -> 3.2.15`	No	No Known Exploit
731/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 8.2	SQL Injection SNYK-PYTHON-DJANGO-2606969	`django:` `2.2.26 -> 3.2.15`	No	Proof of Concept
776/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.1	SQL Injection SNYK-PYTHON-DJANGO-2940618	`django:` `2.2.26 -> 3.2.15`	No	Proof of Concept
564/1000 Why? Has a fix available, CVSS 7	Reflected File Download (RFD) SNYK-PYTHON-DJANGO-2968205	`django:` `2.2.26 -> 3.2.15`	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 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

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS) 🦉 Denial of Service (DoS) 🦉 SQL Injection 🦉 More lessons are available in Snyk Learn