[Security] Bump rack from 2.0.6 to 2.2.1

[dependabot-preview]

Bumps rack from 2.0.6 to 2.2.1. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Low severity vulnerability that affects rack There's a possible information leak / session hijack vulnerability in Rack. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session.

The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.

Impact

The session id stored in a cookie is the same id that is used when querying the backing session storage engine. Most storage mechanisms (for example a database) use some sort of indexing in order to speed up the lookup of that id. By carefully timing requests and session lookup failures, an attacker may be able to perform a timing attack to determine an existing session id and hijack that session.

Releases

The 1.6.12 and 2.0.8 releases are available at the normal locations.

Workarounds

There are no known workarounds.

Patches

To aid users who aren't able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a

... (truncated)

Affected versions: >= 2.0.0, < 2.0.8

Sourced from The Ruby Advisory Database.

Possible information leak / session hijack vulnerability There's a possible information leak / session hijack vulnerability in Rack.

Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session.

The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.

Impact:

The session id stored in a cookie is the same id that is used when querying the backing session storage engine. Most storage mechanisms (for example a database) use some sort of indexing in order to speed up the lookup of that id. By carefully timing requests and session lookup failures, an attacker may be able to perform a timing attack to determine an existing session id and hijack that session.

Patched versions: ~> 1.6.12; >= 2.0.8 Unaffected versions: none

Changelog

Sourced from rack's changelog.

[2.2.1] - 2020-02-09

Fixed

• Rework Rack::Request#ip to handle empty forwarded_for. (#1577, @ioquatix)

[2.2.0] - 2020-02-08

SPEC Changes

• rack.session request environment entry must respond to to_hash and return unfrozen Hash. (@jeremyevans)
• Request environment cannot be frozen. (@jeremyevans)
• CGI values in the request environment with non-ASCII characters must use ASCII-8BIT encoding. (@jeremyevans)
• Improve SPEC/lint relating to SERVER_NAME, SERVER_PORT and HTTP_HOST. (#1561, @ioquatix)

Added

• rackup supports multiple -r options and will require all arguments. (@jeremyevans)
• Server supports an array of paths to require for the :require option. (@khotta)
• Files supports multipart range requests. (@fatkodima)
• Multipart::UploadedFile supports an IO-like object instead of using the filesystem, using :filename and :io options. (@jeremyevans)
• Multipart::UploadedFile supports keyword arguments :path, :content_type, and :binary in addition to positional arguments. (@jeremyevans)
• Static supports a :cascade option for calling the app if there is no matching file. (@jeremyevans)
• Session::Abstract::SessionHash#dig. (@jeremyevans)
• Response.[] and MockResponse.[] for creating instances using status, headers, and body. (@ioquatix)
• Convenient cache and content type methods for Rack::Response. (#1555, @ioquatix)

Changed

• Request#params no longer rescues EOFError. (@jeremyevans)
• Directory uses a streaming approach, significantly improving time to first byte for large directories. (@jeremyevans)
• Directory no longer includes a Parent directory link in the root directory index. (@jeremyevans)
• QueryParser#parse_nested_query uses original backtrace when reraising exception with new class. (@jeremyevans)
• ConditionalGet follows RFC 7232 precedence if both If-None-Match and If-Modified-Since headers are provided. (@jeremyevans)
• .ru files supports the frozen-string-literal magic comment. (@eregon)
• Rely on autoload to load constants instead of requiring internal files, make sure to require 'rack' and not just 'rack/...'. (@jeremyevans)
• Etag will continue sending ETag even if the response should not be cached. (@henm)
• Request#host_with_port no longer includes a colon for a missing or empty port. (@AlexWayfer)
• All handlers uses keywords arguments instead of an options hash argument. (@ioquatix)
• Files handling of range requests no longer return a body that supports to_path, to ensure range requests are handled correctly. (@jeremyevans)
• Multipart::Generator only includes Content-Length for files with paths, and Content-Disposition filename if the UploadedFile instance has one. (@jeremyevans)
• Request#ssl? is true for the wss scheme (secure websockets). (@jeremyevans)
• Rack::HeaderHash is memoized by default. (#1549, @ioquatix)
• Rack::Directory allow directory traversal inside root directory. (#1417, @ThomasSevestre)
• Sort encodings by server preference. (#1184, @ioquatix, @wjordan)
• Rework host/hostname/authority implementation in Rack::Request. #host and #host_with_port have been changed to correctly return IPv6 addresses formatted with square brackets, as defined by RFC3986. (#1561, @ioquatix)
• Rack::Builder parsing options on first #\ line is deprecated. (#1574, @ioquatix)

Removed

... (truncated)

Commits

• 961d976 Prepare point release.
• 2d00d05 Add CHANGELOG entry for #1577.
• f8fd024 Update CHANGELOG to include 2.2.0.
• 21e7aac Rework Request#ip to handle empty forwarded_for.
• 39d501a fix release task
• ceab14f Update SPEC filename in gemspec
• b500b84 Update links.
• 1d5f8df Tidy up gemspec.
• 9045515 Deprecate option parsing in config.ru files.
• 84b2181 Update CHANGELOG to include 2.1.2
• 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)

[dependabot-preview]

Superseded by #8.