Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Fix for 20 vulnerabilities #1

Merged
merged 1 commit into from
Nov 17, 2020

Conversation

snyk-bot
Copy link

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

✨ Snyk has automatically assigned this pull request, set who gets assigned.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • Gemfile
⚠️ Warning
Failed to update the Gemfile.lock, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 679/1000
Why? Has a fix available, CVSS 9.3
Denial of Service (DoS)
SNYK-RUBY-JSON-560838
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Denial of Service (DoS)
SNYK-RUBY-NOKOGIRI-20214
No No Known Exploit
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Denial of Service (DoS)
SNYK-RUBY-NOKOGIRI-20245
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Arbitrary Code Execution
SNYK-RUBY-NOKOGIRI-20277
No No Known Exploit
medium severity 601/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Sensitive Information Exposure
SNYK-RUBY-NOKOGIRI-20292
No Proof of Concept
high severity 579/1000
Why? Has a fix available, CVSS 7.3
XML External Entity (XXE) Injection
SNYK-RUBY-NOKOGIRI-20299
No No Known Exploit
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Arbitrary Code Execution
SNYK-RUBY-NOKOGIRI-20367
No No Known Exploit
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Out of Bounds Memory Write
SNYK-RUBY-NOKOGIRI-20368
No No Known Exploit
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Use of vulnerable libxml2
SNYK-RUBY-NOKOGIRI-20432
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-RUBY-NOKOGIRI-22013
No No Known Exploit
high severity 654/1000
Why? Has a fix available, CVSS 8.8
Denial of Service (DoS)
SNYK-RUBY-NOKOGIRI-22014
No No Known Exploit
high severity 619/1000
Why? Has a fix available, CVSS 8.1
Command Injection
SNYK-RUBY-NOKOGIRI-459107
No No Known Exploit
high severity 659/1000
Why? Has a fix available, CVSS 8.9
Uncontrolled Memory Allocation
SNYK-RUBY-NOKOGIRI-534637
No No Known Exploit
high severity 600/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-RUBY-NOKOGIRI-552159
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-RUBY-NOKOGIRI-72433
No No Known Exploit
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Information Exposure
SNYK-RUBY-RACK-538324
No No Known Exploit
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Directory Traversal
SNYK-RUBY-RACK-569066
No No Known Exploit
medium severity 646/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.5
Cross-site Request Forgery (CSRF)
SNYK-RUBY-RACK-572377
No Proof of Concept
medium severity 519/1000
Why? Has a fix available, CVSS 6.1
Cross-site Scripting (XSS)
SNYK-RUBY-RACK-72567
No No Known Exploit
low severity 379/1000
Why? Has a fix available, CVSS 3.3
Insecure Use of /tmp directory
SNYK-RUBY-RUBOCOP-20447
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

👩‍💻 Set who automatically gets assigned

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

@dregules dregules merged this pull request into master Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants