[Security] Bump actionpack from 4.2.10 to 6.1.3.1

[dependabot-preview[bot]]

Bumps actionpack from 4.2.10 to 6.1.3.1. This update includes security fixes.

Vulnerabilities fixed

Sourced from The Ruby Advisory Database.

Ability to forge per-form CSRF tokens given a global CSRF token It is possible to possible to, given a global CSRF token such as the one present in the authenticity_token meta tag, forge a per-form CSRF token for any action for that session.

Versions Affected: rails < 5.2.5, rails < 6.0.4 Not affected: Applications without existing HTML injection vulnerabilities. Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1

Impact

Given the ability to extract the global CSRF token, an attacker would be able to construct a per-form CSRF token for that session.

Workarounds

This is a low-severity security issue. As such, no workaround is necessarily until such time as the application can be upgraded.

Patched versions: ~> 5.2.4.3; >= 6.0.3.1 Unaffected versions: none

Sourced from The Ruby Advisory Database.

Possible Strong Parameters Bypass in ActionPack There is a strong parameters bypass vector in ActionPack.

Versions Affected: rails <= 6.0.3 Not affected: rails < 4.0.0 Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1

Impact

In some cases user supplied information can be inadvertently leaked from Strong Parameters. Specifically the return value of each, or each_value, or each_pair will return the underlying "untrusted" hash of data that was read from the parameters. Applications that use this return value may be inadvertently use untrusted user input.

Impacted code will look something like this:

def update
  # Attacker has included the parameter: `{ is_admin: true }`
  User.update(clean_up_params)
</tr></table> 

... (truncated)

Patched versions: ~> 5.2.4.3; >= 6.0.3.1 Unaffected versions: < 4.0.0

Sourced from The Ruby Advisory Database.

Possible Strong Parameters Bypass in ActionPack There is a strong parameters bypass vector in ActionPack.

Versions Affected: rails <= 6.0.3 Not affected: rails < 4.0.0 Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1

Impact

In some cases user supplied information can be inadvertently leaked from Strong Parameters. Specifically the return value of each, or each_value, or each_pair will return the underlying "untrusted" hash of data that was read from the parameters. Applications that use this return value may be inadvertently use untrusted user input.

Impacted code will look something like this:

def update
  # Attacker has included the parameter: `{ is_admin: true }`
  User.update(clean_up_params)
</tr></table> 

... (truncated)

Patched versions: ~> 5.2.4, >= 5.2.4.3; >= 6.0.3.1 Unaffected versions: < 4.0.0

Sourced from The Ruby Advisory Database.

Ability to forge per-form CSRF tokens given a global CSRF token It is possible to possible to, given a global CSRF token such as the one present in the authenticity_token meta tag, forge a per-form CSRF token for any action for that session.

Versions Affected: rails < 5.2.5, rails < 6.0.4 Not affected: Applications without existing HTML injection vulnerabilities. Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1

Impact

Given the ability to extract the global CSRF token, an attacker would be able to construct a per-form CSRF token for that session.

Workarounds

This is a low-severity security issue. As such, no workaround is necessarily until such time as the application can be upgraded.

Patched versions: ~> 5.2.4, >= 5.2.4.3; >= 6.0.3.1 Unaffected versions: none

Release notes

Sourced from actionpack's releases.

6.1.3.1

Active Support

• No changes.

Active Model

• No changes.

Active Record

• No changes.

Action View

• No changes.

Action Pack

• No changes.

Active Job

• No changes.

Action Mailer

• No changes.

Action Cable

• No changes.

... (truncated)

Changelog

Sourced from actionpack's changelog.

Rails 6.1.3.1 (March 26, 2021)

• No changes.

Rails 6.1.3 (February 17, 2021)

• Re-define routes when not set correctly via inheritance.

  John Hawthorn

Rails 6.1.2.1 (February 10, 2021)

• Prevent open redirect when allowed host starts with a dot

  [CVE-2021-22881]

  Thanks to @tktech (https://hackerone.com/tktech) for reporting this issue and the patch!

  Aaron Patterson

Rails 6.1.2 (February 09, 2021)

• Fix error in ActionController::LogSubscriber that would happen when throwing inside a controller action.

  Janko Marohnić

• Fix fixture_file_upload deprecation when file_fixture_path is a relative path.

  Eugene Kenny

Rails 6.1.1 (January 07, 2021)

• Fix nil translation key lookup in controllers/

  Jan Klimo

• Quietly handle unknown HTTP methods in Action Dispatch SSL middleware.

  Alex Robbin

• Change the request method to a GET when passing failed requests down to config.exceptions_app.

  Alex Robbin

... (truncated)

Commits

• 85c6823 v6.1.3.1
• 5aaaa16 Preparing for 6.1.3 release
• e322277 Merge pull request #41463 from jhawthorn/isolated_engine_controller_subclasses
• eddb809 Merge pull request #41441 from jonathanhefner/apidocs-inline-code-markup
• 32064ab Remove unnessary escape char in Regexp
• 130c128 Preparing for 6.1.2.1 release
• b5de7b3 Prevent open redirect when allowed host starts with a dot
• bf8c59c Preparing for 6.1.2 release
• 42ad010 Merge pull request #41280 from kentakag/fix-raw-params-method-to-not-raise-an...
• 04d6ac8 Merge pull request #41223 from janko/controller-throw-log-subscriber
• 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 #93.