What is CVE-2020-36629?

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

How severe is CVE-2020-36629?

CVE-2020-36629 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of httpster are affected by CVE-2020-36629?

httpster (npm) versions < 1.1.0 is affected.

Is there a fix for CVE-2020-36629?

Yes. CVE-2020-36629 is fixed in 1.1.0. Upgrade to this version or later.

Is CVE-2020-36629 exploitable, and should I be worried?

Whether CVE-2020-36629 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-2020-36629 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-2020-36629 in httpster

Q: How severe is CVE-2020-36629?

CVE-2020-36629 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of httpster are affected by CVE-2020-36629?

httpster (npm) versions < 1.1.0 is affected.

Q: Is there a fix for CVE-2020-36629?

Yes. CVE-2020-36629 is fixed in 1.1.0. Upgrade to this version or later.

Q: Is CVE-2020-36629 exploitable, and should I be worried?

Whether CVE-2020-36629 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-2020-36629 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-2020-36629?

Upgrade httpster to 1.1.0 or later.

Summary

SimbCo httpster vulnerable to Path Traversal

A vulnerability classified as critical was found in SimbCo httpster. This vulnerability affects the function fs.realpathSync of the file src/server.coffee. The manipulation leads to path traversal. The exploit has been disclosed to the public and may be used. The name of the patch is d3055b3e30b40b65d30c5a06d6e053dffa7f35d0. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-216748.

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.

CVE-2020-36629 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.0); upgrading removes the vulnerable code path.

Affected versions

httpster (< 1.1.0)

Security releases

httpster → 1.1.0 (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 httpster to 1.1.0 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-2020-36629? CVE-2020-36629 is a high-severity path traversal vulnerability in httpster (npm), affecting versions < 1.1.0. It is fixed in 1.1.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
How severe is CVE-2020-36629? CVE-2020-36629 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of httpster are affected by CVE-2020-36629? httpster (npm) versions < 1.1.0 is affected.
Is there a fix for CVE-2020-36629? Yes. CVE-2020-36629 is fixed in 1.1.0. Upgrade to this version or later.
Is CVE-2020-36629 exploitable, and should I be worried? Whether CVE-2020-36629 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-2020-36629 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-2020-36629? Upgrade httpster to 1.1.0 or later.