CVE-2017-16109 json
Directory Traversal in easyquick
published 8y ago modified 4mo ago also GHSA-8h55-49jm-739x , EUVD-2018-0383
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
easyquick is a simple web server. easyquick is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url. Access is constrained, however, to supported file types. Requesting a file such as /etc/passwd returns a "not supported" error.
Is CVE-2017-16109 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/easyquick referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | easyquick | <=0.1.1 |
no fix listed |
Affected products
- HackerOne easyquick node module
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/JacksonGL/NPM-Vuln-PoC/tree/master/directory-traversal/easyquick
web, exploit, third-party-advisory
-
nodesecurity.io
/advisories/373
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-16109
advisory
-
github.com
/advisories/GHSA-8h55-49jm-739x
advisory
-
npmjs.com
/advisories/373
web
Sources
- CVE List CVE-2017-16109
- GitHub Advisory GHSA-8h55-49jm-739x
- NVD CVE-2017-16109
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.