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

2021-09-29T00:56:15-04:00

snyk-bot commented

2021-09-29 00:56:15 -04:00

(Migrated from github.com)

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	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	XML External Entity (XXE) Injection SNYK-RUBY-NOKOGIRI-1726792	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

<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 | 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 | XML External Entity (XXE) Injection <br/>[SNYK-RUBY-NOKOGIRI-1726792](https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792) | 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=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiI0NDdhNjk1Zi1lMGUwLTQ0MjEtYTNlZC02OGY1MzBmNmQ1MzIiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6IjQ0N2E2OTVmLWUwZTAtNDQyMS1hM2VkLTY4ZjUzMGY2ZDUzMiJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/atomaka/project/39f5769a-2ee8-4777-a1bb-509dcee65a10?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/atomaka/project/39f5769a-2ee8-4777-a1bb-509dcee65a10?utm_source=github&utm_medium=referral&page=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":"447a695f-e0e0-4421-a3ed-68f530f6d532","prPublicId":"447a695f-e0e0-4421-a3ed-68f530f6d532","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-1726792"],"upgrade":["SNYK-RUBY-NOKOGIRI-1726792"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[661]})

This pull request can be merged automatically.

You are not authorized to merge this pull request.

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b snyk-fix-1ef81a45e777b69b6c8bedd4ca39be04 master

git pull origin snyk-fix-1ef81a45e777b69b6c8bedd4ca39be04

Step 2:

Merge the changes and update on Gitea.

git checkout master

git merge --no-ff snyk-fix-1ef81a45e777b69b6c8bedd4ca39be04

git push origin master

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No Assignees

1 Participants

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#33