What is CVE-2015-5688?

CVE-2015-5688 is a high-severity path traversal vulnerability in geddy (npm), affecting versions < 13.0.8. It is fixed in 13.0.8. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

Which versions of geddy are affected by CVE-2015-5688?

geddy (npm) versions < 13.0.8 is affected.

Is there a fix for CVE-2015-5688?

Yes. CVE-2015-5688 is fixed in 13.0.8. Upgrade to this version or later.

Is CVE-2015-5688 exploitable, and should I be worried?

Whether CVE-2015-5688 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-2015-5688 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-2015-5688 in geddy

Q: Which versions of geddy are affected by CVE-2015-5688?

geddy (npm) versions < 13.0.8 is affected.

Q: Is there a fix for CVE-2015-5688?

Yes. CVE-2015-5688 is fixed in 13.0.8. Upgrade to this version or later.

Q: Is CVE-2015-5688 exploitable, and should I be worried?

Whether CVE-2015-5688 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-2015-5688 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-2015-5688?

Upgrade geddy to 13.0.8 or later.

CVE-2015-5688

CVE-2015-5688 is a high-severity path traversal vulnerability in geddy (npm), affecting versions < 13.0.8. It is fixed in 13.0.8.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Directory Traversal in geddy

Versions 13.0.8 and earlier of geddy are vulnerable to a directory traversal attack via URI encoded attack vectors.

Proof of Concept

http://localhost:4000/..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fetc/passwd

Update geddy to version >= 13.0.8

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

geddy (< 13.0.8)

Security releases

geddy → 13.0.8 (npm)

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