CVE-2016-0752
Ruby on Rails Directory Traversal Vulnerability
Rails Ruby on Rails
Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 25 March 2022. US federal agencies were required to remediate it by 15 April 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 95.5%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2016-0752 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2016-0752.
What does CVE-2016-0752 affect?
CVE-2016-0752 affects Rails Ruby on Rails. Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.
How severe is CVE-2016-0752?
CVE-2016-0752 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 95.5%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 April 2022.
How should organisations respond to CVE-2016-0752?
Apply the vendor patch for Rails Ruby on Rails as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.