Skip to content

[Snyk] Security upgrade github-pages from 224 to 225 #64

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

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

Conversation

tf-security
Copy link

snyk-top-banner

Snyk has created this PR to fix 26 vulnerabilities in the rubygems dependencies of this project.

Snyk changed the following file(s):

  • Gemfile
  • Gemfile.lock

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Stack-based Buffer Overflow
SNYK-RUBY-NOKOGIRI-8732769
  202  
high severity Use After Free
SNYK-RUBY-NOKOGIRI-8732779
  202  
medium severity Use After Free
SNYK-RUBY-NOKOGIRI-9510795
  202  
medium severity Denial of Service (DoS)
SNYK-RUBY-COMMONMARKER-5829860
  163  
high severity Heap-based Buffer Overflow
SNYK-RUBY-NOKOGIRI-7164639
  159  
high severity Directory Traversal
SNYK-RUBY-TZINFO-2958048
  143  
medium severity Denial of Service (DoS)
SNYK-RUBY-COMMONMARKER-3318400
  138  
medium severity Use After Free
SNYK-RUBY-NOKOGIRI-9510789
  130  
high severity NULL Pointer Dereference
SNYK-RUBY-NOKOGIRI-3052880
  115  
high severity Improper Restriction of XML External Entity Reference ('XXE')
SNYK-RUBY-REXML-7814166
  111  
medium severity Use After Free
SNYK-RUBY-NOKOGIRI-6228056
  85  
medium severity Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-RUBY-REXML-7577227
  68  
medium severity Cross-site Scripting (XSS)
SNYK-RUBY-ACTIVESUPPORT-3360028
  66  
low severity Cross-site Scripting (XSS)
SNYK-RUBY-NOKOGIRI-8453714
  64  
medium severity Denial of Service (DoS)
SNYK-RUBY-COMMONMARKER-5603112
  58  
medium severity Denial of Service (DoS)
SNYK-RUBY-COMMONMARKER-3318401
  55  
low severity Buffer Under-read
SNYK-RUBY-NOKOGIRI-9789079
  50  
medium severity Uncontrolled Resource Consumption
SNYK-RUBY-REXML-6861566
  50  
medium severity Denial of Service (DoS)
SNYK-RUBY-REXML-7577228
  49  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-RUBY-REXML-8309365
  49  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-RUBY-ACTIVESUPPORT-3237242
  46  
low severity Out-of-bounds Read
SNYK-RUBY-COMMONMARKER-3318398
  43  
medium severity Information Exposure
SNYK-RUBY-ACTIVESUPPORT-5851458
  41  
medium severity Denial of Service (DoS)
SNYK-RUBY-COMMONMARKER-5603111
  41  
medium severity Denial of Service (DoS)
SNYK-RUBY-REXML-7462086
  40  
medium severity Denial of Service (DoS)
SNYK-RUBY-COMMONMARKER-3318399
  37  

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Cross-site Scripting (XSS)
🦉 Use After Free
🦉 More lessons are available in Snyk Learn

@tf-security tf-security requested a review from a team as a code owner June 21, 2025 05:04
@tf-security
Copy link
Author

tf-security commented Jun 21, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

code/snyk check is complete. No issues have been found. (View Details)

Copy link

gitstream-cm bot commented Jun 21, 2025

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

Copy link

gitstream-cm bot commented Jun 21, 2025

🥷 Code experts: No results found

No code experts were identified for the files in this pull request based on git blame analysis.

This may occur when:

  • Files are new or have limited commit history
  • Git authors aren't mapped to current team members
  • Analysis thresholds need adjustment

If you expected to see expert suggestions, consider:

  • Reviewing your config.user_mapping settings
  • Adjusting the gt/lt parameters in your action
  • Verifying files have sufficient commit history

To learn more about /:\gitStream - Visit our Docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants