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

[Snyk] Security upgrade poltergeist from 1.16.0 to 1.16.0 #37

Open
snyk-bot wants to merge 1 commit from snyk-fix-5809b442593801e225b5b5ab04e91be7 into master
pull from: snyk-fix-5809b442593801e225b5b5ab04e91be7
merge into: atomaka:master
Conversation 0 Commits 1 Files changed 1 +27 -21
snyk-bot commented 2022-04-12 12:06:38 -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
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5		 Regular Expression Denial of Service (ReDoS)
SNYK-RUBY-NOKOGIRI-2620374		 No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5		 Out-of-bounds Write
SNYK-RUBY-NOKOGIRI-2630623		 No No Known Exploit
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5		 Denial of Service (DoS)
SNYK-RUBY-NOKOGIRI-2630898		 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

<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 :-------------------------:|-------------------------|:-------------------------|:-------------------------|:------------------------- ![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 | Regular Expression Denial of Service (ReDoS) <br/>[SNYK-RUBY-NOKOGIRI-2620374](https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374) | 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 | Out-of-bounds Write <br/>[SNYK-RUBY-NOKOGIRI-2630623](https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623) | 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-NOKOGIRI-2630898](https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898) | 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=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiIxZDJhMDI2Zi1lZGZlLTRmOWYtOTIwYS03MDJjN2I3N2EyNmIiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6IjFkMmEwMjZmLWVkZmUtNGY5Zi05MjBhLTcwMmM3Yjc3YTI2YiJ9fQ==" 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":"1d2a026f-edfe-4f9f-920a-702c7b77a26b","prPublicId":"1d2a026f-edfe-4f9f-920a-702c7b77a26b","dependencies":[{"name":"poltergeist","from":"1.16.0","to":"1.16.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-2620374","SNYK-RUBY-NOKOGIRI-2630623","SNYK-RUBY-NOKOGIRI-2630898"],"upgrade":["SNYK-RUBY-NOKOGIRI-2620374","SNYK-RUBY-NOKOGIRI-2630623","SNYK-RUBY-NOKOGIRI-2630898"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[661,661,661]}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Learn about vulnerability in an interactive lesson of Snyk Learn.](https://learn.snyk.io?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-5809b442593801e225b5b5ab04e91be7:snyk-fix-5809b442593801e225b5b5ab04e91be7
git checkout snyk-fix-5809b442593801e225b5b5ab04e91be7

Merge

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

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?