Information Exposure Affecting actionview package, versions >=4.3.0, <5.0.0>=4.2.0, <4.2.5.1>=3.2.23, <4.1.14.1<3.2.22.1
Threat Intelligence
Snyk has a published code exploit for this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RUBY-ACTIONVIEW-20262
- published24 Jan 2016
- disclosed24 Jan 2016
- creditJohn Poulin
Introduced: 24 Jan 2016
CVE-2016-0752 (opens in a new tab)Overview
actionview is a conventions and helpers gem for building web pages.
Affected versions of this Gem are vulnerable to directory traversal and information leaks.
Details
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.
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]) endprivate def verify_template(name)
add verification logic particular to your application here
end