atomaka/link-share
1
0
Fork 0
Code Issues Pull requests 42 Releases Activity

[Snyk] Fix for 3 vulnerabilities #56

Open
snyk-bot wants to merge 1 commit from snyk-fix-93bbbca6fb961a4beaf62abc97b8c696 into master
pull from: snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
merge into: atomaka:master
Conversation 0 Commits 1 Files changed 1 +60 -56
snyk-bot commented 2023-03-14 12:17:51 -04:00 (Migrated from github.com)
Copy link

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

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • Gemfile.lock

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 486/1000
Why? Recently disclosed, Has a fix available, CVSS 4		 Out-of-Bounds
SNYK-RUBY-NOKOGIRI-3357692		 No No Known Exploit
medium severity 601/1000
Why? Recently disclosed, Has a fix available, CVSS 6.3		 Access Control Bypass
SNYK-RUBY-NOKOGIRI-3357693		 No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-RUBY-RACK-3356639		 No No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

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:

🦉 Access Control Bypass
🦉 Denial of Service (DoS)

<h3>Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.</h3> #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - Gemfile.lock #### Vulnerabilities that will be fixed ##### With an upgrade: Severity | Priority Score (*) | Issue | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | **486/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 4 | Out-of-Bounds <br/>[SNYK-RUBY-NOKOGIRI-3357692](https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-3357692) | No | No Known Exploit ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | **601/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 6.3 | Access Control Bypass <br/>[SNYK-RUBY-NOKOGIRI-3357693](https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-3357693) | No | No Known Exploit ![high severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/h.png "high severity") | **661/1000** <br/> **Why?** Recently disclosed, Has a fix available, CVSS 7.5 | Denial of Service (DoS) <br/>[SNYK-RUBY-RACK-3356639](https://snyk.io/vuln/SNYK-RUBY-RACK-3356639) | No | No Known Exploit (*) Note that the real score may have changed since the PR was raised. 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: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiI5OThiZWZmMi01MmJkLTRmMTQtOTIxZi05ZTU0NmNhYzYwNTkiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6Ijk5OGJlZmYyLTUyYmQtNGYxNC05MjFmLTllNTQ2Y2FjNjA1OSJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/atomaka/project/39f5769a-2ee8-4777-a1bb-509dcee65a10?utm_source&#x3D;github&amp;utm_medium&#x3D;referral&amp;page&#x3D;fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/atomaka/project/39f5769a-2ee8-4777-a1bb-509dcee65a10?utm_source&#x3D;github&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":"998beff2-52bd-4f14-921f-9e546cac6059","prPublicId":"998beff2-52bd-4f14-921f-9e546cac6059","dependencies":[{"name":"poltergeist","from":"1.16.0","to":"1.16.0"},{"name":"sinatra","from":"2.0.0","to":"2.0.0"},{"name":"sinatra-activerecord","from":"2.0.13","to":"2.0.13"},{"name":"sinatra-contrib","from":"2.0.0","to":"2.0.0"},{"name":"sinatra-flash","from":"0.3.0","to":"0.3.0"}],"packageManager":"rubygems","projectPublicId":"39f5769a-2ee8-4777-a1bb-509dcee65a10","projectUrl":"https://app.snyk.io/org/atomaka/project/39f5769a-2ee8-4777-a1bb-509dcee65a10?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-RUBY-NOKOGIRI-3357692","SNYK-RUBY-NOKOGIRI-3357693","SNYK-RUBY-RACK-3356639"],"upgrade":["SNYK-RUBY-NOKOGIRI-3357692","SNYK-RUBY-NOKOGIRI-3357693","SNYK-RUBY-RACK-3356639"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["priorityScore"],"priorityScoreList":[486,601,661],"remediationStrategy":"vuln"}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Access Control Bypass](https://learn.snyk.io/lessons/broken-access-control/cpp/?loc&#x3D;fix-pr) 🦉 [Denial of Service (DoS)](https://learn.snyk.io/lessons/redos/javascript/?loc&#x3D;fix-pr)
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-93bbbca6fb961a4beaf62abc97b8c696:snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git checkout snyk-fix-93bbbca6fb961a4beaf62abc97b8c696

Merge

Merge the changes and update on Forgejo.
git checkout master
git merge --no-ff snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git checkout snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git rebase master
git checkout master
git merge --ff-only snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git checkout snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git rebase master
git checkout master
git merge --no-ff snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git checkout master
git merge --squash snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git checkout master
git merge --ff-only snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
git checkout master
git merge snyk-fix-93bbbca6fb961a4beaf62abc97b8c696
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.

Reference: atomaka/link-share#56
No description provided.
Delete branch "snyk-fix-93bbbca6fb961a4beaf62abc97b8c696"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?