Which versions of hubl-server are affected by CVE-2017-16035?

hubl-server (npm) versions <= 1.1.5 is affected.

Is there a fix for CVE-2017-16035?

No fixed version is listed for CVE-2017-16035 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2017-16035 exploitable, and should I be worried?

Whether CVE-2017-16035 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-2017-16035 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-2017-16035 in hubl-server

Q: What is CVE-2017-16035?

CVE-2017-16035 is a high-severity security vulnerability in hubl-server (npm), affecting versions <= 1.1.5. No fixed version is listed yet.

Q: Is there a fix for CVE-2017-16035?

No fixed version is listed for CVE-2017-16035 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2017-16035 exploitable, and should I be worried?

Whether CVE-2017-16035 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-2017-16035 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-2017-16035

CVE-2017-16035 is a high-severity security vulnerability in hubl-server (npm), affecting versions <= 1.1.5. No fixed version is listed yet.

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

hubl-server downloads resources over HTTP

Affected versions of hubl-server insecurely download dependencies over an unencrypted HTTP connection.

In scenarios where an attacker has a privileged network position, it is possible to intercept the responses and replace the dependencies with malicious ones, resulting in code execution on the system running hubl-server.

Impact

Affected versions

hubl-server (<= 1.1.5)

Security releases

Not available

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

No patch is currently available for this vulnerability, and it has not seen any updates since 2015.

The best mitigation is currently to avoid using this package, using a different package if available.

Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised yo

Frequently Asked Questions

What is CVE-2017-16035? CVE-2017-16035 is a high-severity security vulnerability in hubl-server (npm), affecting versions <= 1.1.5. No fixed version is listed yet.
Which versions of hubl-server are affected by CVE-2017-16035? hubl-server (npm) versions <= 1.1.5 is affected.
Is there a fix for CVE-2017-16035? No fixed version is listed for CVE-2017-16035 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2017-16035 exploitable, and should I be worried? Whether CVE-2017-16035 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-2017-16035 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.