8000 [Snyk] Security upgrade ruby from 3.1 to 3.4.4 by mikolajroszak · Pull Request #2 · mikolajroszak/nokogiri · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Snyk] Security upgrade ruby from 3.1 to 3.4.4 #2

New issue
8000

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mikolajroszak
Copy link
Owner

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

  • oci-images/nokogiri-test/mri-3.1.dockerfile

We recommend upgrading to ruby:3.4.4, as this image has only 197 known vulnerabilities. To do this, merge this pull request, then 8000 verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
low severity Inappropriate Encoding for Output Context
SNYK-DEBIAN12-OPENSSH-1556053
  295  
low severity OS Command Injection
SNYK-DEBIAN12-IMAGEMAGICK-5660573
  288  
low severity OS Command Injection
SNYK-DEBIAN12-IMAGEMAGICK-5660573
  288  
low severity OS Command Injection
SNYK-DEBIAN12-IMAGEMAGICK-5660573
  288  
low severity OS Command Injection
SNYK-DEBIAN12-IMAGEMAGICK-5660573
  288  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 OS Command Injection

Micro-Learning Topic: OS command injection (Detected by phrase)

Matched on "OS Command Injection"

What is this? (2min video)

In many situations, applications will rely on OS provided functions, scripts, macros and utilities instead of reimplementing them in code. While functions would typically be accessed through a native interface library, the remaining three OS provided features will normally be invoked via the command line or launched as a process. If unsafe inputs are used to construct commands or arguments, it may allow arbitrary OS operations to be performed that can compromise the server.

Try a challenge in Secure Code Warrior

Helpful references
  • OWASP Command Injection - OWASP community page with comprehensive information about command injection, and links to various OWASP resources to help detect or prevent it.
  • OWASP testing for Command Injection - This article is focused on providing testing techniques for identifying command injection flaws in your applications

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
0