sonarcloud[bot]
commented
2 years ago Kudos, SonarCloud Quality Gate passed! 
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
No Duplication information
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/dev.txt⚠️ Warning
``` django-debug-toolbar 1.2.2 requires django, which is not installed. django-debug-toolbar 1.2.2 requires sqlparse, which is not installed. ```**Why?** Has a fix available, CVSS 3.1 | Directory Traversal
[SNYK-PYTHON-DJANGO-1066259](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1066259) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **379/1000**
**Why?** Has a fix available, CVSS 3.3 | Directory Traversal
[SNYK-PYTHON-DJANGO-1279042](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1279042) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **579/1000**
**Why?** Has a fix available, CVSS 7.3 | HTTP Header Injection
[SNYK-PYTHON-DJANGO-1290072](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1290072) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **589/1000**
**Why?** Has a fix available, CVSS 7.5 | Directory Traversal
[SNYK-PYTHON-DJANGO-1298665](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-1298665) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **479/1000**
**Why?** Has a fix available, CVSS 5.3 | Access Restriction Bypass
[SNYK-PYTHON-DJANGO-2312875](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2312875) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **399/1000**
**Why?** Has a fix available, CVSS 3.7 | Directory Traversal
[SNYK-PYTHON-DJANGO-2329158](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2329158) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **399/1000**
**Why?** Has a fix available, CVSS 3.7 | Information Exposure
[SNYK-PYTHON-DJANGO-2329159](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2329159) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **479/1000**
**Why?** Has a fix available, CVSS 5.3 | Denial of Service (DoS)
[SNYK-PYTHON-DJANGO-2329160](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2329160) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **424/1000**
**Why?** Has a fix available, CVSS 4.2 | Cross-site Scripting (XSS)
[SNYK-PYTHON-DJANGO-2389002](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2389002) | `django:`
`1.11.29 -> 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](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2389021) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **624/1000**
**Why?** Has a fix available, CVSS 8.2 | SQL Injection
[SNYK-PYTHON-DJANGO-2606966](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2606966) | `django:`
`1.11.29 -> 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](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2606969) | `django:`
`1.11.29 -> 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](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2940618) | `django:`
`1.11.29 -> 3.2.15`
| No | Proof of Concept  | **564/1000**
**Why?** Has a fix available, CVSS 7 | Reflected File Download (RFD)
[SNYK-PYTHON-DJANGO-2968205](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2968205) | `django:`
`1.11.29 -> 3.2.15`
| No | No Known Exploit  | **589/1000**
**Why?** Has a fix available, CVSS 7.5 | Regular Expression Denial of Service (ReDoS)
[SNYK-PYTHON-SQLPARSE-1584201](https://snyk.io/vuln/SNYK-PYTHON-SQLPARSE-1584201) | `sqlparse:`
`0.3.1 -> 0.4.2`
| 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: