What is CVE-2016-1000305?

CVE-2016-1000305 is a medium-severity path traversal vulnerability in guard-livereload (rubygems), affecting versions < 2.5.2. It is fixed in 2.5.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

Which versions of guard-livereload are affected by CVE-2016-1000305?

guard-livereload (rubygems) versions < 2.5.2 is affected.

Is there a fix for CVE-2016-1000305?

Yes. CVE-2016-1000305 is fixed in 2.5.2. Upgrade to this version or later.

Is CVE-2016-1000305 exploitable, and should I be worried?

Whether CVE-2016-1000305 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-2016-1000305 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-2016-1000305 in guard-livereload

Q: Which versions of guard-livereload are affected by CVE-2016-1000305?

guard-livereload (rubygems) versions < 2.5.2 is affected.

Q: Is there a fix for CVE-2016-1000305?

Yes. CVE-2016-1000305 is fixed in 2.5.2. Upgrade to this version or later.

Q: Is CVE-2016-1000305 exploitable, and should I be worried?

Whether CVE-2016-1000305 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-2016-1000305 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-2016-1000305?

Upgrade guard-livereload to 2.5.2 or later.

Summary

guard-livereload has a directory traversal vulnerability

The vulnerability allows remote attackers to read arbitrary files
on the server by exploiting improper path validation in the
livereload server functionality.

This vulnerability is related to the handling of file paths in the
livereload server component, which could allow an attacker to traverse
directories and access files outside the intended web root directory.

The issue was identified and reported through the DWF (Distributed
Weakness Filing) project, which assigns CVE identifiers for
security vulnerabilities.

A directory traversal vulnerability exists in
guard-livereload before version 2.5.2.

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

guard-livereload (< 2.5.2)

Security releases

guard-livereload → 2.5.2 (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 guard-livereload to 2.5.2 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2016-1000305? CVE-2016-1000305 is a medium-severity path traversal vulnerability in guard-livereload (rubygems), affecting versions < 2.5.2. It is fixed in 2.5.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
Which versions of guard-livereload are affected by CVE-2016-1000305? guard-livereload (rubygems) versions < 2.5.2 is affected.
Is there a fix for CVE-2016-1000305? Yes. CVE-2016-1000305 is fixed in 2.5.2. Upgrade to this version or later.
Is CVE-2016-1000305 exploitable, and should I be worried? Whether CVE-2016-1000305 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-2016-1000305 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-2016-1000305? Upgrade guard-livereload to 2.5.2 or later.