[Security] Bump railties from 4.2.10 to 6.0.3.3

[dependabot-preview[bot]]

Bumps railties from 4.2.10 to 6.0.3.3. This update includes a security fix.

Vulnerabilities fixed

Sourced from The Ruby Advisory Database.

Possible Remote Code Execution Exploit in Rails Development Mode There is a possible a possible remote code executing exploit in Rails when in development mode. This vulnerability has been assigned the CVE identifier CVE-2019-5420.

Versions Affected: 6.0.0.X, 5.2.X. Not affected: None. Fixed Versions: 6.0.0.beta3, 5.2.2.1

Impact

With some knowledge of a target application it is possible for an attacker to guess the automatically generated development mode secret token. This secret token can be used in combination with other Rails internals to escalate to a remote code execution exploit.

All users running an affected release should either upgrade or use one of the workarounds immediately.

Releases

Patched versions: ~> 5.2.2, >= 5.2.2.1; >= 6.0.0.beta3 Unaffected versions: none

Release notes

Sourced from railties's releases.

6.0.3.3

Active Support

• No changes.

Active Model

• No changes.

Active Record

• No changes.

Action View

• [CVE-2020-8185] Fix potential XSS vulnerability in the translate/t helper.

Action Pack

• No changes.

Active Job

• No changes.

Action Mailer

• No changes.

Action Cable

• No changes.

Active Storage

• No changes.

Action Mailbox

Changelog

Sourced from railties's changelog.

Rails 6.0.3.3 (September 09, 2020)

• No changes.

Rails 6.0.3.2 (June 17, 2020)

• No changes.

Rails 6.0.3.1 (May 18, 2020)

• No changes.

Rails 6.0.3 (May 06, 2020)

• Cache compiled view templates when running tests by default

  When generating a new app without --skip-spring, caching classes is disabled in environments/test.rb. This implicitly disables caching view templates too. This change will enable view template caching by adding this to the generated environments/test.rb:

  config.action_view.cache_template_loading = true
  

  Jorge Manrubia

• Rails::Application#eager_load! is available again to load application code manually as it was possible in previous versions.

  Please, note this is not integrated with the whole eager loading logic that runs when Rails boots with eager loading enabled, you can think of this method as a vanilla recursive code loader.

  This ability has been restored because there are some use cases for it, such as indexers that need to have all application classes and modules in memory.

  Xavier Noria

• Generators that inherit from NamedBase respect --force option

  Josh Brody

• Regression fix: The Rake task zeitwerk:check supports eager loaded namespaces which do not have eager load paths, like the recently added i18n. These namespaces are only required to respond to eager_load!.

Commits

• 070d4af v6.0.3.3
• fbe2433 Preparing for 6.0.3.2 release
• 34991a6 Preparing for 6.0.3.1 release
• 2c8fe2a bumping version, updating changelog
• b738f19 Preparing for 6.0.3 release
• 509b9da Preparing for 6.0.3.rc1 release
• c549fb4 Backports improved warning in zeitwerk:check
• e29372a Merge pull request #38970 from eugeneius/tmp_pids_keepfile
• 5bf69b4 Merge pull request #38794 from cromulus/mandrill-ingress-tokenfix
• b60571e Merge pull request #38864 from abhaynikam/replace-mailing-list-url
• 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](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #45.