[Security] Bump yard from 0.9.14 to 0.9.26

[dependabot-preview]

Bumps yard from 0.9.14 to 0.9.26. This update includes security fixes.

Vulnerabilities fixed

Sourced from The Ruby Advisory Database.

Arbitrary path traversal and file access via yard server A path traversal vulnerability was discovered in YARD <= 0.9.19 when using yard server to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions.

The issue is resolved in v0.9.20 and later.

Patched versions: >= 0.9.20 Unaffected versions: none

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects yard

Possible arbitrary path traversal and file access via yard server

Impact

A path traversal vulnerability was discovered in YARD <= 0.9.19 when using yard server to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions.

Thanks to CuongMX from Viettel Cyber Security for discovering this vulnerability.

Patches

Please upgrade to YARD v0.9.20 immediately if you are relying on yard server to host documentation in any untrusted environments.

Workarounds

For users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level. WEBrick, for example, can perform such sanitization by default (which you can use via yard server -s webrick), as can certain rules in your webserver configuration.

Affected versions: < 0.9.20

Sourced from The Ruby Advisory Database.

Possible arbitrary path traversal and file access via yard server A path traversal vulnerability was discovered in YARD <= 0.9.19 when using yard server to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions.

Patched versions: >= 0.9.20 Unaffected versions: none

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects yard

Possible arbitrary path traversal and file access via yard server

Impact

A path traversal vulnerability was discovered in YARD <= 0.9.19 when using yard server to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions.

Thanks to CuongMX from Viettel Cyber Security for discovering this vulnerability.

Patches

Please upgrade to YARD v0.9.20 immediately if you are relying on yard server to host documentation in any untrusted environments.

Workarounds

For users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level. WEBrick, for example, can perform such sanitization by default (which you can use via yard server -s webrick), as can certain rules in your webserver configuration.

Affected versions: < 0.9.20

Release notes

Sourced from yard's releases.

Release v0.9.26

• Add support for Ruby 3.0 and fix tests
• Fix support for frozen_string_literal: false magic comments (#1363)

Release v0.9.25

• Fix parsing issue with conditional blocks mixed with conditional modifiers. (#1308, #1324, #1326, #1327)
• Add table of contents IDs to redcarpet generated markdown. (#1323)
• Backport fixes for Ruby 1.9 (#1320)
• Fix parsing of checksums in yard server (#1301)
• Map Ruby C variable error names to Ruby classes (#1270, #1275)
• Fix initialization of RDocMarkup across threads (#1318)
• Remove warning for Kernel#open (#1312)
• Omit spec files in gem package (#1307)
• README updates (#1322)

Release v0.9.24

• Add {YARD::CodeObjects::NamespaceMapper.on_invalidate} callback when separator cache is changed.
• Fix issue where Registry fails to resolve first-time lookups on instance methods.

Release v0.9.23

• Fix issues with double encoded code blocks when highlighted from an extra file.

Release v0.9.22

• Revert jquery update in last release since it requires more changes. (#1298)

Release v0.9.21

• Updates to add support for Ruby 2.7.0 (#1290, #1296)
• Fix parsing of multiline method signatures (#1220)
• Remove RubyGems post install message (#1269)
• Improve object deletion from RegistryStore (#1284)

Changelog

Sourced from yard's changelog.

0.9.26 - December 26th, 2020

• Add support for Ruby 3.0 and fix tests
• Fix support for frozen_string_literal: false magic comments (#1363)

0.9.25 - May 3rd, 2020

• Fix parsing issue with conditional blocks mixed with conditional modifiers. (#1308, #1324, #1326, #1327)
• Add table of contents IDs to redcarpet generated markdown. (#1323)
• Backport fixes for Ruby 1.9 (#1320)
• Fix parsing of checksums in yard server (#1301)
• Map Ruby C variable error names to Ruby classes (#1270, #1275)
• Fix initialization of RDocMarkup across threads (#1318)
• Remove warning for Kernel#open (#1312)
• Omit spec files in gem package (#1307)
• README updates (#1322)

0.9.24 - January 8th, 2020

• Add {YARD::CodeObjects::NamespaceMapper.on_invalidate} callback when separator cache is changed.
• Fix issue where Registry fails to resolve first-time lookups on instance methods.

0.9.23 - January 5th, 2020

• Fix issues with double encoded code blocks when highlighted from an extra file.

0.9.22 - December 31st, 2019

• Revert jquery update in last release since it requires more changes. (#1298)

0.9.21 - December 31st, 2019

• Updates to add support for Ruby 2.7.0 (#1290, #1296)
• Fix parsing of multiline method signatures (#1220)
• Remove RubyGems post install message (#1269)

Commits

• d202e9d Tag release v0.9.26
• 064a7bc Modify samus to prep tag but not publish gem
• 3409f0c Fix permissions
• 5b85a7c Update changelog
• 14411e8 Remove inadvertently added subtrees
• bdf84a3 Add runs-on for actions
• 7fca83b Merge pull request #1364 from lsegal/ruby3
• e38755d Remove utf8 test
• 1518c0e Add spec for single-line methods
• fb2c885 Fix specs on Ruby 3
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)