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

[Snyk] Fix for 1 vulnerabilities #22

Open
snyk-bot wants to merge 1 commit from snyk-fix-1125126ac6e8d74da6f24a5445cf1826 into master
pull from: snyk-fix-1125126ac6e8d74da6f24a5445cf1826
merge into: atomaka:master
Conversation 0 Commits 1 Files changed 2 +63 -58
snyk-bot commented 2020-06-22 23:51:30 -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
    • Gemfile.lock

Vulnerabilities that will be fixed

With an upgrade:
Severity Issue Breaking Change Exploit Maturity
medium severity Cross-site Request Forgery (CSRF)
SNYK-RUBY-RACK-572377		 No Proof of Concept

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

<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 - Gemfile.lock #### Vulnerabilities that will be fixed ##### With an upgrade: Severity | Issue | Breaking Change | Exploit Maturity :-------------------------:|:-------------------------|:-------------------------|:------------------------- ![medium severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/m.png "medium severity") | Cross-site Request Forgery (CSRF) <br/>[SNYK-RUBY-RACK-572377](https://snyk.io/vuln/SNYK-RUBY-RACK-572377) | No | Proof of Concept 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=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJmMjMwMjNlMy01Y2QzLTQyNzQtOWEyYi01NjRlMWUzMjc5OWIiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImYyMzAyM2UzLTVjZDMtNDI3NC05YTJiLTU2NGUxZTMyNzk5YiJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/atomaka/project/39f5769a-2ee8-4777-a1bb-509dcee65a10) 🛠 [Adjust project settings](https://app.snyk.io/org/atomaka/project/39f5769a-2ee8-4777-a1bb-509dcee65a10/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":"f23023e3-5cd3-4274-9a2b-564e1e32799b","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=fix-pr","type":"auto","patch":[],"vulns":["SNYK-RUBY-RACK-572377"],"upgrade":["SNYK-RUBY-RACK-572377"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":[]})
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-1125126ac6e8d74da6f24a5445cf1826:snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git checkout snyk-fix-1125126ac6e8d74da6f24a5445cf1826

Merge

Merge the changes and update on Forgejo.
git checkout master
git merge --no-ff snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git checkout snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git rebase master
git checkout master
git merge --ff-only snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git checkout snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git rebase master
git checkout master
git merge --no-ff snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git checkout master
git merge --squash snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git checkout master
git merge --ff-only snyk-fix-1125126ac6e8d74da6f24a5445cf1826
git checkout master
git merge snyk-fix-1125126ac6e8d74da6f24a5445cf1826
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#22
No description provided.
Delete branch "snyk-fix-1125126ac6e8d74da6f24a5445cf1826"

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?