{"answers":{"affected":"2 open source packages ship an affected version, including elding. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16222 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16222 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16222 is a medium-severity path traversal vulnerability in HackerOne elding node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16222 and fix it if it is affected.\n\nWhat it is: CVE-2017-16222 is a medium-severity path traversal vulnerability in HackerOne elding node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-16222 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- elding (npm): affected all versions up to 1.0.0; no fix listed\n- elding (npm): affected all versions up to 1.0.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-16222/ (Markdown: https://insights.sbomify.com/CVE-2017-16222/index.md)","id":"CVE-2017-16222","markdown":"https://insights.sbomify.com/CVE-2017-16222/index.md","name":"CVE-2017-16222","record":{"aliases":["GHSA-rp28-29ch-gh92"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js web server","requires_auth":"none","summary":"An attacker can read arbitrary files with extensions from the server filesystem via directory traversal in the elding web server library.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"elding","vendor":"elding_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"elding is a simple web server. elding is vulnerable to a directory traversal issue, allowing an attacker to access the filesystem by placing \"../\" in the url. The files accessible, however, are limited to files with a file extension. Sending a GET request to /../../../etc/passwd, for example, will return a 404 on etc/passwd/index.js.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Directory Traversal in elding","id":"CVE-2017-16222","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Directory Traversal in nodeaaaaa","id":"CVE-2017-16223"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"elding","purl":null,"source":"GHSA-rp28-29ch-gh92"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"elding","purl":"pkg:npm/elding","source":"GHSA-rp28-29ch-gh92"}],"prev":{"headline":"Directory Traversal in yzt","id":"CVE-2017-16221"},"products":["elding node module"],"published":"2018-06-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["HackerOne"]},"summary":"An attacker can read arbitrary files with extensions from the server filesystem via directory traversal in the elding web server library.","url":"https://insights.sbomify.com/CVE-2017-16222/"}