Created by: dependabot-preview[bot]
Bumps actionview from 5.2.2 to 5.2.2.1. This update includes security fixes.
Vulnerabilities fixed
Sourced from The Ruby Advisory Database.
Denial of Service Vulnerability in Action View There is a potential denial of service vulnerability in actionview. This vulnerability has been assigned the CVE identifier CVE-2019-5419.
Impact
Specially crafted accept headers can cause the Action View template location code to consume 100% CPU, causing the server unable to process requests. This impacts all Rails applications that render views.
All users running an affected release should either upgrade or use one of the workarounds immediately.
Workarounds
This vulnerability can be mitigated by wrapping
rendercalls withrespond_toblocks. For example, the following example is vulnerable:class UserController < ApplicationController def index </tr></table> ... (truncated) Patched versions: >= 6.0.0.beta3; \~> 5.2.2, >= 5.2.2.1; \~> 5.1.6, >= 5.1.6.2; \~> 5.0.7, >= 5.0.7.2; \~> 4.2.11, >= 4.2.11.1 Unaffected versions: none
Sourced from The GitHub Security Advisory Database.
High severity vulnerability that affects actionview
File Content Disclosure in Action View
Impact
There is a possible file content disclosure vulnerability in Action View. Specially crafted accept headers in combination with calls to
render file:can cause arbitrary files on the target server to be rendered, disclosing the file contents.The impact is limited to calls to
renderwhich render file contents without a specified accept format. Impacted code in a controller looks something like this:... (truncated)class UserController < ApplicationController def index render file: "#{Rails.root}/some/file" end endAffected versions: >= 5.2.0, <= 5.2.2
Sourced from The GitHub Security Advisory Database.
Critical severity vulnerability that affects actionview
Denial of Service Vulnerability in Action View
Impact
Specially crafted accept headers can cause the Action View template location code to consume 100% CPU, causing the server unable to process requests. This impacts all Rails applications that render views.
All users running an affected release should either upgrade or use one of the workarounds immediately.
Releases
The 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations.
Workarounds
This vulnerability can be mitigated by wrapping
... (truncated)rendercalls withrespond_toblocks. For example, the following example is vulnerable:Affected versions: >= 5.2.0, <= 5.2.2
Commits
-
e69ff43Prep release -
7f5ccdaFix possible dev mode RCE -
d7fac9cOnly accept formats from registered mime types - See full diff 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot ignore this [patch|minor|major] versionwill close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill 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 labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language -
@dependabot badge mewill 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)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- 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.