{"answers":{"affected":"2 open source packages ship an affected version, including yttivy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16219 is a high-severity path traversal vulnerability in HackerOne yttivy 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-16219 and fix it if it is affected.\n\nWhat it is: CVE-2017-16219 is a high-severity path traversal vulnerability in HackerOne yttivy 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-16219 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- yttivy (npm): affected from 0.0.0; no fix listed\n- yttivy (npm): affected from 0.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-16219/ (Markdown: https://insights.sbomify.com/CVE-2017-16219/index.md)","id":"CVE-2017-16219","markdown":"https://insights.sbomify.com/CVE-2017-16219/index.md","name":"CVE-2017-16219","record":{"aliases":["GHSA-96qc-ghj4-rq27"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js static file server","requires_auth":"none","summary":"An attacker can read arbitrary files from the server filesystem by exploiting a directory traversal vulnerability in the yttivy static file server.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"yttivy","vendor":"yttivy_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"yttivy is a static file server. yttivy is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing \"../\" in the url.","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 yttivy","id":"CVE-2017-16219","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 wind-mvc","id":"CVE-2017-16220"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"yttivy","purl":null,"source":"GHSA-96qc-ghj4-rq27"},{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"yttivy","purl":"pkg:npm/yttivy","source":"GHSA-96qc-ghj4-rq27"}],"prev":{"headline":"Directory Traversal in dgard8.lab6","id":"CVE-2017-16218"},"products":["yttivy 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-16","vendors":["HackerOne"]},"summary":"An attacker can read arbitrary files from the server filesystem by exploiting a directory traversal vulnerability in the yttivy static file server.","url":"https://insights.sbomify.com/CVE-2017-16219/"}