CVE-2017-16014

Http-proxy is a proxying library. Because of the way errors are handled in versions before 0.7.0, an attacker that forces an error can crash the server, causing a denial of service.

Published: 2018-06-04 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-16014 is rated Moderate Risk (57.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.69%). EPSS rose +1.41% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-16014

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.27% 1.69% +1.41%
2 2025-03-30 0.94% 0.27% -0.66%
3 2025-03-29 — 0.94% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-16014

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2017-16014

GitHub Security Advisory for CVE-2017-16014

GHSA-9xw9-pvgv-6p76 · Severity: high · Ecosystem: npm — Insufficient Error Handling in http-proxy

OS Trackers for CVE-2017-16014

vendor priority summary link
debian unimportant CVE-2017-16014 unimportant priority: Debian including 1 source packages (node-http-proxy), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 4. https://security-tracker.debian.org/tracker/CVE-2017-16014
redhat medium — https://access.redhat.com/security/cve/CVE-2017-16014

Affected software / configurations for CVE-2017-16014

Vendor Product Version Raw CPE
http-proxy_project http-proxy < 0.7.0 cpe:2.3:a:http-proxy_project:http-proxy:*:*:*:*:*:node.js:*:*

References for CVE-2017-16014

URL Tags
https://github.com/nodejitsu/node-http-proxy/pull/101 Issue Tracking Third Party Advisory
https://nodesecurity.io/advisories/323 Third Party Advisory
cvelogic Threat Intelligence