What is CVE-2014-7819?

CVE-2014-7819 is a medium-severity path traversal vulnerability in sprockets (rubygems), affecting versions < 2.0.5. It is fixed in 2.0.5, 2.1.4, 2.2.3, 2.3.3, 2.4.6, 2.5.1, 2.7.1, 2.8.3, 2.9.4, 2.10.2, 2.11.3, 2.12.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

Which versions of sprockets are affected by CVE-2014-7819?

sprockets (rubygems) versions < 2.0.5 is affected.

Is there a fix for CVE-2014-7819?

Yes. CVE-2014-7819 is fixed in 2.0.5, 2.1.4, 2.2.3, 2.3.3, 2.4.6, 2.5.1, 2.7.1, 2.8.3, 2.9.4, 2.10.2, 2.11.3, 2.12.3. Upgrade to this version or later.

Is CVE-2014-7819 exploitable, and should I be worried?

Whether CVE-2014-7819 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2014-7819 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2014-7819 in sprockets

Q: Which versions of sprockets are affected by CVE-2014-7819?

sprockets (rubygems) versions < 2.0.5 is affected.

Q: Is there a fix for CVE-2014-7819?

Yes. CVE-2014-7819 is fixed in 2.0.5, 2.1.4, 2.2.3, 2.3.3, 2.4.6, 2.5.1, 2.7.1, 2.8.3, 2.9.4, 2.10.2, 2.11.3, 2.12.3. Upgrade to this version or later.

Q: Is CVE-2014-7819 exploitable, and should I be worried?

Whether CVE-2014-7819 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2014-7819 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2014-7819?

Upgrade: sprockets to 2.0.5 or later, sprockets to 2.1.4 or later, sprockets to 2.2.3 or later, sprockets to 2.3.3 or later, sprockets to 2.4.6 or later, sprockets to 2.5.1 or later, sprockets to 2.7.1 or later, sprockets to 2.8.3 or later, sprockets to 2.9.4 or later, sprockets to 2.10.2 or later, sprockets to 2.11.3 or later, sprockets to 2.12.3 or later.

Summary

sprockets vulnerable to Path Traversal

Multiple directory traversal vulnerabilities in server.rb in Sprockets before 2.0.5, 2.1.x before 2.1.4, 2.2.x before 2.2.3, 2.3.x before 2.3.3, 2.4.x before 2.4.6, 2.5.x before 2.5.1, 2.6.x and 2.7.x before 2.7.1, 2.8.x before 2.8.3, 2.9.x before 2.9.4, 2.10.x before 2.10.2, 2.11.x before 2.11.3, 2.12.x before 2.12.3, and 3.x before 3.0.0.beta.3, as distributed with Ruby on Rails 3.x and 4.x, allow remote attackers to determine the existence of files outside the application root via a ../ (dot dot slash) sequence with (1) double slashes or (2) URL encoding.

Impact

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Affected versions

sprockets (< 2.0.5) sprockets (>= 2.1.0, < 2.1.4) sprockets (>= 2.2.0, < 2.2.3) sprockets (>= 2.3.0, < 2.3.3) sprockets (>= 2.4.0, < 2.4.6) sprockets (>= 2.5.0, < 2.5.1) sprockets (>= 2.6.0, < 2.7.1) sprockets (>= 2.8.0, < 2.8.3) sprockets (>= 2.9.0, < 2.9.4) sprockets (>= 2.10.0, < 2.10.2) sprockets (>= 2.11.0, < 2.11.3) sprockets (>= 2.12.0, < 2.12.3)

Security releases

sprockets → 2.0.5 (rubygems) sprockets → 2.1.4 (rubygems) sprockets → 2.2.3 (rubygems) sprockets → 2.3.3 (rubygems) sprockets → 2.4.6 (rubygems) sprockets → 2.5.1 (rubygems) sprockets → 2.7.1 (rubygems) sprockets → 2.8.3 (rubygems) sprockets → 2.9.4 (rubygems) sprockets → 2.10.2 (rubygems) sprockets → 2.11.3 (rubygems) sprockets → 2.12.3 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

sprockets to 2.0.5 or later; sprockets to 2.1.4 or later; sprockets to 2.2.3 or later; sprockets to 2.3.3 or later; sprockets to 2.4.6 or later; sprockets to 2.5.1 or later; sprockets to 2.7.1 or later; sprockets to 2.8.3 or later; sprockets to 2.9.4 or later; sprockets to 2.10.2 or later; sprockets to 2.11.3 or later; sprockets to 2.12.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2014-7819? CVE-2014-7819 is a medium-severity path traversal vulnerability in sprockets (rubygems), affecting versions < 2.0.5. It is fixed in 2.0.5, 2.1.4, 2.2.3, 2.3.3, 2.4.6, 2.5.1, 2.7.1, 2.8.3, 2.9.4, 2.10.2, 2.11.3, 2.12.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
Which versions of sprockets are affected by CVE-2014-7819? sprockets (rubygems) versions < 2.0.5 is affected.
Is there a fix for CVE-2014-7819? Yes. CVE-2014-7819 is fixed in 2.0.5, 2.1.4, 2.2.3, 2.3.3, 2.4.6, 2.5.1, 2.7.1, 2.8.3, 2.9.4, 2.10.2, 2.11.3, 2.12.3. Upgrade to this version or later.
Is CVE-2014-7819 exploitable, and should I be worried? Whether CVE-2014-7819 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2014-7819 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2014-7819?
- Upgrade sprockets to 2.0.5 or later
- Upgrade sprockets to 2.1.4 or later
- Upgrade sprockets to 2.2.3 or later
- Upgrade sprockets to 2.3.3 or later
- Upgrade sprockets to 2.4.6 or later
- Upgrade sprockets to 2.5.1 or later
- Upgrade sprockets to 2.7.1 or later
- Upgrade sprockets to 2.8.3 or later
- Upgrade sprockets to 2.9.4 or later
- Upgrade sprockets to 2.10.2 or later
- Upgrade sprockets to 2.11.3 or later
- Upgrade sprockets to 2.12.3 or later

Other vulnerabilities in sprockets

CVE-IDSeverityPackage summary

CVE-2018-3760Highsprockets: Sprockets path traversal leads to information leak