CVE-2016-10528

CVE-2016-10528 is a medium-severity path traversal vulnerability in restafary (npm), affecting versions < 1.6.1. It is fixed in 1.6.1.

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 restafary

Affected versions of restafary are susceptible to a directory traversal vulnerability when a root path is specified in the configuration.

Proof of Concept

curl -i -s -k  -X 'GET' -H 'Authorization: Basic YWRtaW46cGFzc3dvcmQ=' 'http://localhost:8000/api/v1/fs/..%2f..%2fetc/passwd'

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

restafary (< 1.6.1)

Security releases

restafary → 1.6.1 (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 environmentNew to Kodem? Get a demo →

Remediation advice

Update to version 1.6.1 or later.

Frequently Asked Questions

  1. What is CVE-2016-10528? CVE-2016-10528 is a medium-severity path traversal vulnerability in restafary (npm), affecting versions < 1.6.1. It is fixed in 1.6.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. Which versions of restafary are affected by CVE-2016-10528? restafary (npm) versions < 1.6.1 is affected.
  3. Is there a fix for CVE-2016-10528? Yes. CVE-2016-10528 is fixed in 1.6.1. Upgrade to this version or later.
  4. Is CVE-2016-10528 exploitable, and should I be worried? Whether CVE-2016-10528 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
  5. What actually determines whether CVE-2016-10528 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.
  6. How do I fix CVE-2016-10528? Upgrade restafary to 1.6.1 or later.

Stop the waste.
Protect your environment with Kodem.