[Security] Bump activestorage from 6.0.3 to 6.1.3

[dependabot-preview]

Bumps activestorage from 6.0.3 to 6.1.3. This update includes a security fix.

Vulnerabilities fixed

Sourced from The Ruby Advisory Database.

Circumvention of file size limits in ActiveStorage There is a vulnerability in ActiveStorage's S3 adapter that allows the Content-Length of a direct file upload to be modified by an end user.

Versions Affected: rails < 5.2.4.2, rails < 6.0.3.1 Not affected: Applications that do not use the direct upload functionality of the ActiveStorage S3 adapter. Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1

Impact

Utilizing this vulnerability, an attacker can control the Content-Length of an S3 direct upload URL without receiving a new signature from the server. This could be used to bypass controls in place on the server to limit upload size.

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

Release notes

Sourced from activestorage's releases.

6.1.3

Active Support

• No changes.

Active Model

• No changes.

Active Record

• Fix the MySQL adapter to always set the right collation and charset to the connection session.

  Rafael Mendonça França

• Fix MySQL adapter handling of time objects when prepared statements are enabled.

  Rafael Mendonça França

• Fix scoping in enum fields using conditions that would generate an IN clause.

  Ryuta Kamizono

• Skip optimised #exist? query when #include? is called on a relation with a having clause

  Relations that have aliased select values AND a having clause that references an aliased select value would generate an error when #include? was called, due to an optimisation that would generate call #exists? on the relation instead, which effectively alters the select values of the query (and thus removes the aliased select values), but leaves the having clause intact. Because the having clause is then referencing an aliased column that is no longer present in the simplified query, an ActiveRecord::InvalidStatement error was raised.

  An sample query affected by this problem:

  Author.select('COUNT(*) as total_posts', 'authors.*')
        .joins(:posts)
        .group(:id)

... (truncated)

Changelog

Sourced from activestorage's changelog.

Rails 6.1.3 (February 17, 2021)

• No changes.

Rails 6.1.2.1 (February 10, 2021)

• No changes.

Rails 6.1.2 (February 09, 2021)

• No changes.

Rails 6.1.1 (January 07, 2021)

• Fix S3 multipart uploads when threshold is larger than file.

  Matt Muller

Rails 6.1.0 (December 09, 2020)

• Change default queue name of the analysis (:active_storage_analysis) and purge (:active_storage_purge) jobs to be the job adapter's default (:default).

  Rafael Mendonça França

• Implement strict_loading on ActiveStorage associations.

  David Angulo

• Remove deprecated support to pass :combine_options operations to ActiveStorage::Transformers::ImageProcessing.

  Rafael Mendonça França

• Remove deprecated ActiveStorage::Transformers::MiniMagickTransformer.

  Rafael Mendonça França

• Remove deprecated config.active_storage.queue.

  Rafael Mendonça França

• Remove deprecated ActiveStorage::Downloading.

  Rafael Mendonça França

• Add per-environment configuration support

... (truncated)

Commits

• 5aaaa16 Preparing for 6.1.3 release
• 130c128 Preparing for 6.1.2.1 release
• bf8c59c Preparing for 6.1.2 release
• 1514745 Resolve conflict
• 5181300 Restore ActiveStorage::Blob#find_signed
• 9386cb0 Rename master to main in all code references
• 5f3ff60 Preparing for 6.1.1 release
• ccf5d99 Fix S3 multipart uploads when threshold is larger than file
• 914caca Preparing for 6.1.0 release
• 3930449 Change default queue name of all the internal jobs to be the job adapter's de...
• 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)