Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.5 CISA Known Exploited Vulnerability

CVE-2014-0130

Ruby on Rails Directory Traversal Vulnerability

Rails Ruby on Rails

Directory traversal vulnerability in actionpack/lib/abstract_controller/base.rb in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.

CVSS
7.5
HIGH
EPSS
53.7%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
7 May 2014
CWE-22

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 53.7%, which is higher than 99% 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-2014-0130 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2014-0130.

What does CVE-2014-0130 affect?

CVE-2014-0130 affects Rails Ruby on Rails. Directory traversal vulnerability in actionpack/lib/abstract_controller/base.rb in the implicit-render implementation in Ruby on Rails before 3.2.18, 4.0.x before 4.0.5, and 4.1.x before 4.1.1, when certain route globbing configurations are enabled, allows remote attackers to read arbitrary files via a crafted request.

How severe is CVE-2014-0130?

CVE-2014-0130 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 53.7%, higher than 99% 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-2014-0130?

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.