self-healing-infrastructure/core
1
0
Fork 0
Code Issues Pull requests 11 Projects Releases Packages Wiki Activity

[Snyk] Security upgrade django from 3.1.4 to 3.2.12 #6

Open
arno.birchler wants to merge 1 commit from snyk-fix-c929b32ee9385cb9d968c5e044306108 into master
pull from: snyk-fix-c929b32ee9385cb9d968c5e044306108
merge into: self-healing-infrastructure:master
Conversation 0 Commits 1 Files changed 1 +1 -1
arno.birchler commented 2022-02-01 23:30:34 +00:00 (Migrated from gitlab.com)
Copy link

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this Merge Request

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • requirements.txt
⚠️ Warning 
django-health-check 3.16.5 requires django, which is not installed.
django-dbbackup 3.3.0 requires Django, which is not installed.

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.4 -> 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.4 -> 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 Merge Request 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

<h3>Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.</h3> #### Changes included in this Merge Request - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - requirements.txt <details> <summary>⚠️ <b>Warning</b></summary> ``` django-health-check 3.16.5 requires django, which is not installed. django-dbbackup 3.3.0 requires Django, which is not installed. ``` </details> #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | **496/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 4.2 | Cross-site Scripting (XSS) <br/>[SNYK-PYTHON-DJANGO-2389002](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2389002) | `django:` <br> `3.1.4 -> 3.2.12` <br> | No | No Known Exploit ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | **551/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 5.3 | Denial of Service (DoS) <br/>[SNYK-PYTHON-DJANGO-2389021](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-2389021) | `django:` <br> `3.1.4 -> 3.2.12` <br> | 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 Merge Request 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: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJjMjJkZDVhOC05NjlkLTQwYzEtOWU4OS00MGZiMzUxN2RjMzciLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImMyMmRkNWE4LTk2OWQtNDBjMS05ZTg5LTQwZmIzNTE3ZGMzNyJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/arnobirchler/project/f12b01b7-4014-4eb1-9519-9384068cbae1?utm_source&#x3D;gitlab&amp;utm_medium&#x3D;referral&amp;page&#x3D;fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/arnobirchler/project/f12b01b7-4014-4eb1-9519-9384068cbae1?utm_source&#x3D;gitlab&amp;utm_medium&#x3D;referral&amp;page&#x3D;fix-pr/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # (snyk:metadata:{"prId":"c22dd5a8-969d-40c1-9e89-40fb3517dc37","prPublicId":"c22dd5a8-969d-40c1-9e89-40fb3517dc37","dependencies":[{"name":"django","from":"3.1.4","to":"3.2.12"}],"packageManager":"pip","projectPublicId":"f12b01b7-4014-4eb1-9519-9384068cbae1","projectUrl":"https://app.snyk.io/org/arnobirchler/project/f12b01b7-4014-4eb1-9519-9384068cbae1?utm_source=gitlab&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-DJANGO-2389002","SNYK-PYTHON-DJANGO-2389021"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","pr-warning-shown","priorityScore"],"priorityScoreList":[496,551]})
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin snyk-fix-c929b32ee9385cb9d968c5e044306108:snyk-fix-c929b32ee9385cb9d968c5e044306108
git switch snyk-fix-c929b32ee9385cb9d968c5e044306108

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff snyk-fix-c929b32ee9385cb9d968c5e044306108
git switch snyk-fix-c929b32ee9385cb9d968c5e044306108
git rebase master
git switch master
git merge --ff-only snyk-fix-c929b32ee9385cb9d968c5e044306108
git switch snyk-fix-c929b32ee9385cb9d968c5e044306108
git rebase master
git switch master
git merge --no-ff snyk-fix-c929b32ee9385cb9d968c5e044306108
git switch master
git merge --squash snyk-fix-c929b32ee9385cb9d968c5e044306108
git switch master
git merge --ff-only snyk-fix-c929b32ee9385cb9d968c5e044306108
git switch master
git merge snyk-fix-c929b32ee9385cb9d968c5e044306108
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
self-healing-infrastructure/core!6
No description provided.