MediumGHSA-vx9j-46rh-fqr8CVE-2016-2097

actionview contains Path Traversal vulnerability

Published 24 Oct 2017 · Updated 22 Feb 2024

Is your project on an affected actionview?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

actionviewRubyGems
Affected
>=3.0.0 <3.2.22.2
Fixed in
3.2.22.2
Update to the fixed version for your release line, for example:bundle update --conservative actionview # Gemfile: '>= 3.2.22.2'
actionviewRubyGems
Affected
>=4.0.0 <4.1.14.2
Fixed in
4.1.14.2
Update to the fixed version for your release line, for example:bundle update --conservative actionview # Gemfile: '>= 4.1.14.2'
actionpackRubyGems
Affected
>=3.0.0 <3.2.22.2
Fixed in
3.2.22.2
Update to the fixed version for your release line, for example:bundle update --conservative actionpack # Gemfile: '>= 3.2.22.2'
actionpackRubyGems
Affected
>=4.0.0 <4.1.14.2
Fixed in
4.1.14.2
Update to the fixed version for your release line, for example:bundle update --conservative actionpack # Gemfile: '>= 4.1.14.2'

Details

There is a possible directory traversal and information leak vulnerability in Action View. This was meant to be fixed on CVE-2016-0752. However the 3.2 patch was not covering all possible scenarios. This vulnerability has been assigned the CVE identifier CVE-2016-2097.

Versions Affected: 3.2.x, 4.0.x, 4.1.x Not affected: 4.2+ Fixed Versions: 3.2.22.2, 4.1.14.2

Impact ------ Applications that pass unverified user input to the render method in a controller may be vulnerable to an information leak vulnerability.

Impacted code will look something like this:

def index
  render params[:id]
end

Carefully crafted requests can cause the above code to render files from unexpected places like outside the application's view directory, and can possibly escalate this to a remote code execution attack.

All users running an affected release should either upgrade or use one of the workarounds immediately.

Releases -------- The FIXED releases are available at the normal locations.

Workarounds ----------- A workaround to this issue is to not pass arbitrary user input to the render method. Instead, verify that data before passing it to the render method.

For example, change this:

def index
  render params[:id]
end

To this:

def index
  render verify_template(params[:id])
end

private
def verify_template(name)
  # add verification logic particular to your application here
end

Patches ------- To aid users who aren't able to upgrade immediately we have provided patches for it. It is in git-am format and consist of a single changeset.

  • 3-2-render_data_leak_2.patch - Patch for 3.2 series
  • 4-1-render_data_leak_2.patch - Patch for 4.1 series

Credits ------- Thanks to both Jyoti Singh and Tobias Kraze from makandra for reporting this and working with us in the patch!

Is GHSA-vx9j-46rh-fqr8 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected actionview, and gives you the command that fixes it.

More advisories for actionview

  • MediumCVE-2026-126078Action View: Possible XSS vulnerability in highlight helper · 12 Nov 2026
  • MediumCVE-2026-126070Action View: Possible XSS vulnerability in strip_tags · 12 Nov 2026
  • MediumCVE-2026-126079Action View: Possible XSS vulnerability in text helpers · 12 Nov 2026
  • MediumCVE-2026-126069Action View: Possible XSS vulnerability in tag helpers · 12 Nov 2026
  • LowCVE-2026-33168Rails has a possible XSS vulnerability in its Action View tag helpers · 23 Mar 2026
  • MediumCVE-2023-23913rails-ujs vulnerable to DOM Based Cross-site Scripting contenteditable HTML Elements · 9 Jun 2023
All 17 advisories for actionview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.