[Security] Bump devise from 2.2.4 to 3.5.10

[dependabot-preview]

Bumps devise from 2.2.4 to 3.5.10. This update includes security fixes.

Vulnerabilities fixed

Sourced from The Ruby Advisory Database.

CSRF token fixation attacks in Devise
Devise contains a flaw that allows a remote, user-assisted attacker to
conduct a CSRF token fixation attack. This issue is triggered as previous
CSRF tokens are not properly invalidated when a new token is created.
If an attacker has knowledge of said token, a specially crafted request can
be made to it, allowing the attacker to conduct CSRF attacks.

Patched versions: ~> 2.2.5; >= 3.0.1
Unaffected versions: none

Sourced from The Ruby Advisory Database.

Devise Gem for Ruby Unauthorized Access Using Remember Me Cookie
Devise version before 3.5.4 uses cookies to implement a "Remember me"
functionality. However, it generates the same cookie for all devices. If an
attacker manages to steal a remember me cookie and the user does not change
the password frequently, the cookie can be used to gain access to the
application indefinitely.

Patched versions: >= 3.5.4
Unaffected versions: none

Release notes

Sourced from devise's releases.

v3.5.3

• bug fixes
  • Fix password reset for records where confirmation_required? is disabled and
    confirmation_sent_at is nil. (by @​andygeers)
  • Allow resources with no email field to be recoverable (and do not clear the
    reset password token if the model was already persisted). (by @​seddy, @​stanhu)
• enhancements
  • Upon setting Devise.send_password_change_notification = true a user will receive notification when their password has been changed.

v3.5.2

• enhancements
  • Perform case insensitive basic authorization matching
• bug fixes
  • Do not use digests for password confirmation token
  • Fix infinite redirect in Rails 4.2 authenticated routes
  • Autoload Devise::Encryptor to avoid errors on thread-safe mode
• deprecations
  • config.expire_auth_token_on_timeout was removed

v3.4.1

• enhancements
  • Devise default views now have a similar markup to Rails scaffold views. (by @​udaysinghcode, @​cllns)
  • Passing now: true to the set_flash_message helper now sets the message into
    the flash.now Hash. (by @​hbriggs)
• bugfixes
  • Fixed an regression with translation of flash messages for when the authentication_keys
    config is a Hash. (by @​lucasmazza)

v3.4.0

• enhancements
  • Support added for Rails 4.2. Devise now depends on the responders gem due
    the extraction of the respond_with API from Rails. (by @​lucasmazza)
  • The Simple Form templates follow the same change from 3.3.0 by using Log in and adding
    a hint about the minimum password length when validatable is enabled. (by @​aried3r)
  • Controller generator added as devise:controllers SCOPE. You can use the -c flag
    to pick which controllers (unlocks, confirmations, etc) you want to generate. (by @​Chun-Yang)
  • Removed the hardcoded references for "email" in the flash messages. If you are using
    different attributes as the authentication_keys they will be interpolated in the
    messages instead. (by @​timoschilling)
• bug fix
  • Fixed a regression where the devise generator would fail with a ConnectionNotEstablished
    exception when executed inside a mountable engine. (by @​lucasmazza)
  • Ensure to return symbols in find_scope! fixing a previous regression from 3.3.0 (by @​micat)
  • Ensure all causes of failed login have the same error message (by @​pjungwir)
  • The last_attempt_warning now takes effect when generating the unauthenticated
    message for your users. To keep the current behavior, this flag is now true
    by default. (by @​lucasmazza)

Changelog

Sourced from devise's changelog.

3.5.10 - 2016-05-15

• bug fixes
  • Fix overwriting the remember_token when a valid one already exists (by @​ralinchimev).

3.5.9 - 2016-05-02

• bug fixes
  • Fix strategy checking in Lockable#unlock_strategy_enabled? for :none
    and :undefined strategies. (by @​f3ndot)

3.5.8 - 2016-04-25

• bug fixes
  • Fix the e-mail confirmation instructions send when a user updates the email address from nil

3.5.7 - 2016-04-18

• bug fixes
  • Fix the extend_remember_period configuration. When set to false it does
    not update the cookie expiration anymore.(by @​ulissesalmeida)

3.5.6 - 2016-01-02

• bug fixes
  • Fix type coercion of the rememberable timestamp stored on cookies.

3.5.5 - 2016-22-01

• bug fixes
  • Bring back remember_expired? implementation
  • Ensure timeouts are not triggered if remember me is being used

3.5.4 - 2016-18-01

• bug fixes
  • Store creation timestamps on remember cookies

3.5.3 - 2015-12-10

• bug fixes

  • Fix password reset for records where confirmation_required? is disabled and
    confirmation_sent_at is nil. (by @​andygeers)
  • Allow resources with no email field to be recoverable (and do not clear the
    reset password token if the model was already persisted). (by @​seddy, @​stanhu)

• enhancements

  • Upon setting Devise.send_password_change_notification = true a user will receive notification when their password has been changed.

3.5.2 - 2015-08-10

... (truncated)

Commits

• 321fe1d Release 3.5.10
• a7dcf98 Fix overwriting the remember_token when a valid one already exists (#4101)
• 7e658a2 Release 3.5.9
• 0252f0e Extract list of both strategies into class constant
• 07e907e 🪲 Fix strategy checking in #unlock_strategy_enabled? for :none and und...
• e9ed3e2 Support for older rails versions.
• 2fa6735 Lock mime-types to ~> 2.99
• b8cddc3 Release 3.5.8
• 1d57169 Send confirmation instructions when a user updates the email address from nil
• 812c1de Release 3.5.7 version.
• 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.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it). To ignore the version in this PR you can just close it
• @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)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.