{"answers":{"affected":"2 open source packages ship an affected version, including static-resource-server. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16493 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16493 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16493 is a high-severity path traversal vulnerability in HackerOne static-resource-server, published on 1 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16493 and fix it if it is affected.\n\nWhat it is: CVE-2018-16493 is a high-severity path traversal vulnerability in HackerOne static-resource-server, published on 1 Feb 2019. 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-2018-16493 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- static-resource-server (npm): affected all versions up to 1.7.2; no fix listed\n- static-resource-server (npm): affected all versions up to 1.7.2; 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-2018-16493/ (Markdown: https://insights.sbomify.com/CVE-2018-16493/index.md)","id":"CVE-2018-16493","markdown":"https://insights.sbomify.com/CVE-2018-16493/index.md","name":"CVE-2018-16493","record":{"aliases":["GHSA-45j8-pm75-5v8x"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js static resource server","requires_auth":"none","summary":"An attacker can read arbitrary files on the server by manipulating URL paths in the static-resource-server npm package.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"static-resource-server","vendor":"static-resource-server_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"},{"id":"CWE-548","name":"Exposure of Information Through Directory Listing"}],"description":"A path traversal vulnerability was found in module static-resource-server 1.7.2 that allows unauthorized read access to any file on the server by appending slashes 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":"Path Traversal in simplehttpserver","id":"CVE-2018-16493","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Misconfiguration in Versa VOS","id":"CVE-2018-16494"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.7.2"],"package":"static-resource-server","purl":null,"source":"GHSA-45j8-pm75-5v8x"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.7.2"],"package":"static-resource-server","purl":"pkg:npm/static-resource-server","source":"GHSA-45j8-pm75-5v8x"}],"prev":{"headline":"Prototype Pollution in extend","id":"CVE-2018-16492"},"products":["static-resource-server"],"published":"2019-02-01","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-08-05","vendors":["HackerOne"]},"summary":"An attacker can read arbitrary files on the server by manipulating URL paths in the static-resource-server npm package.","url":"https://insights.sbomify.com/CVE-2018-16493/"}