[Snyk] Fix for 15 vulnerabilities

[naiba4]

Snyk has created this PR to fix 15 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
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5829860	163
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318400	138
	HTTP Request Smuggling SNYK-RUBY-WEBRICK-10500756	130
	Improper Restriction of XML External Entity Reference ('XXE') SNYK-RUBY-REXML-7814166	111
	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-RUBY-REXML-7577227	68
	HTTP Request Smuggling SNYK-RUBY-WEBRICK-8068535	63
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5603112	58
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318401	55
	Denial of Service (DoS) SNYK-RUBY-REXML-7577228	49
	Regular Expression Denial of Service (ReDoS) SNYK-RUBY-REXML-8309365	49
	Uncontrolled Resource Consumption SNYK-RUBY-REXML-6861566	47
	Out-of-bounds Read SNYK-RUBY-COMMONMARKER-3318398	43
	Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5603111	41
	Denial of Service (DoS) SNYK-RUBY-REXML-7462086	40
	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:

🦉 Denial of Service (DoS)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	gem/​jekyll-last-modified-at@​1.3.0 ⏵ 1.3.2
	gem/​jekyll-commonmark@​1.3.1 ⏵ 1.4.0	+2

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		gem/[email protected] Uses eval. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] Uses eval. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is dynamic code execution? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has URL strings. URLs: https://rubygems.org, http://www.google.com/, http://www.example.com/%%30%30, http://www.example.com/, https://www.example.com/, https://www.example.com/foo/bar, https://www.example.com/bar, http://example.com/home/, http://example.com/home/index, http://example.com/, http://example.com/search/an-example-search-query/, http://example.com/a/b/c/, http://example.com/?a=1&b=2&c=3&first=foo, http://example.com/foo, http://example.com/search/, http://example.com/first/second/, http://example.com/a/b/c/?one=1&two=2#foo, http://example.com/a/b/c/#foo, http://example.com/1/, http://example.com/?one=1, http://example.com/?two=2, http://example.com, http://example.com/1, http://example.com/search/Caf%C3%A9/, http://example.com/search/Cafe%CC%81/, http://example.com/search/an+example+search+query/, http://cyberscore.dev/api/users, http://cyberscore.dev/api/users?username=foobaz, HTTP://example.com.:%38%30/%70a%74%68?a=%31#1%323, HTTP://example.com.:80, HTTP://example.com.:80/%70a%74%68?a=%31#1%323, http://example.com/path?a=1#123, http://example.com/path, https://www.example.com:8080, https://www.example.com:8080/, ftp://ftp.is.co.za/rfc/rfc1808.txt, ftp://ftp.is.co.za, http://www.ietf.org/rfc/rfc2396.txt, http://www.ietf.org, http://192.0.2.16:8000, http://example.com:bogus/, http://EXAMPLE.com, http://EXAMPLE.com:80/, http://example.com:/, http://example.com:80/, http://EXAMPLE.COM/, http://example.com/path/, http://elsewhere.com/, http://example.com/relative/path, HTTP://www.w3.org/pub/WWW/TheProject.html, http://www.w3.org, HTTP://example.com/, http://Example.com/, http://example.com/?, http://example.com/#, http://example.com?#, http://example.com./, HTTP://EXAMPLE.COM/, http://www.example.co.uk/, http://www.example.co.uk, http://sub_domain.blogspot.com/, http://sub_domain.blogspot.com, http://example.com/~smith/, http://example.com/%7Esmith/, http://example.com/%7esmith/, http://example.com/%E8, http://example.com/path%2Fsegment/, http://example.com/path/segment/, http://example.com/?%F6, http://example.com/#%F6, http://example.com/%C3%87, http://example.com/C%CC%A7, http://example.com/C%25CC%25A7, http://example.com/%25C3%2587, http://example.com/?q=string, http://example.com:8080/, http://example.com/path/to/, http://example.com:80/path/to/, http://example.com:8080/path/to/, http://example.com:8080, http://example.com:%38%30/, http://example.com/%2E/, http://example.com/../, http://www.example.com///../, http://www.example.com//, http://example.com/path/to/resource/, http://example.com/path/to/resource/sub, http://example.com/path/to/another, http://example.com/path/to/res, http://example.com/to/resource/, http://example.com/file.txt, http://example.com/x, http://example.com/?x=1&y=2, http://elsewhere.com/path/to/, http://newexample.com, http://example.com/path/to/resource?query=x#fragment, http://example.com/search?q=Q%26A, http://example.com/?&x=b, http://example.com/?q=, http://example.com/?&&x=b, http://example.com/?q=a&&x=b, http://example.com/?q&&x=b, http://example.com/?q=a+b, https://example.com/?q=a+b, http://example.com/?q=a%2bb, http://example.com/?v=%7E&w=%&x=%25&y=%2B&z=C%CC%A7, http://example.com/?v=%7E&w=%&x=%25&y=+&z=C%CC%A7, http://example.com/?a=1&a=1, http://example.com/?a=1&a=2, http://example.com/sound%2bvision, http://example.com/indirect/path/./to/../resource/, http://under_score.example.com/, http://www.xn--8ws00zhy3a.com/, http://www.xn--8ws00zhy3a.com, http://www.xn--8ws00zhy3a.com/%20some%20spaces%20/, http://www.xn--8ws00zhy3a.com/atomtests/iri/%E8%A9%B9.html, http://www.xn--n8jaaaaai5bhf7as8fsfk3jnknefdde3f, http://www.comrade.net/path/to/source/, http://www.comrade.co.uk/path/to/source/, http://www.comrade.com/path/to/source/, http://127.0.0.1/, https://example.com/, http://example.com/example.com/, ftp://example.com, http://example.com:21, ftp://example.com:21, http://example.com/path/to/resource, http://7777.example.org:8089 Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has Environment variable access. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has URL strings. URLs: https://github.com/ruby/csv/issues Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has Filesystem access. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has Environment variable access. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] is a AI-detected potential code anomaly. Notes: The code exhibits multiple anomalies, particularly through the use of environment variables, dynamic command execution, and lack of input validation. Caution is advised if considering the use of this code as part of a larger system. Confidence: 1.00 Severity: 0.60 From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] is a AI-detected potential code anomaly. Notes: The script performs legitimate setup tasks but also contains suspicious activities such as downloading and executing binaries from an external source (https://rl.gl) and adding an untrusted repository with the --allow-unauthenticated flag. These actions pose significant security risks, including potential malware and supply chain attacks. Confidence: 1.00 Severity: 0.60 From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has Filesystem access. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has URL strings. URLs: http://rubygems.org, https://developer.apple.com/library/archive/documentation/AppleScript/Conceptual/AppleScriptLangGuide/introduction/ASLR_intro.html, https://developer.roku.com/en-ca/docs/references/brightscript/language/brightscript-language-reference.md, https://docs.gitlab.com/ee/user/project/codeowners/reference.html, https://www.digdag.io/, http://elm-lang.org/, https://godotengine.org/, http://golang.org, http://www.groovy-lang.org/, http://haxe.org, https://github.com/lightbend/config, http://iolanguage.com, http://kotlinlang.org, http://llvm.org/, http://www.lua.org, https://metacpan.org/pod/HTML::Mason, http://www.moonscript.org, http://nim-lang.org/, https://nixos.org/nix/manual/#ch-expression-language, http://en.wikipedia.org/wiki/Prolog, https://rmlatdibris.github.io/, https://svelte.dev/, https://github.com/toml-lang/toml, https://www.typescriptlang.org/ Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has Environment variable access. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		gem/[email protected] has Filesystem access. Location: Package overview From: Gemfile.lock → gem/[email protected] ℹ Read more on: This package | This alert | What is filesystem access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore gem/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report