{"answers":{"affected":"2 open source packages ship an affected version, including st. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16224 in the wild and no public exploit code.","fix":"Upgrade st to 1.2.2 or later.","what":"CVE-2017-16224 is a medium-severity vulnerability in HackerOne st node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-16224 and fix it if it is affected.\n\nWhat it is: CVE-2017-16224 is a medium-severity vulnerability in HackerOne st node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-16224 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- st (npm): affected all versions; fixed in 1.2.2\n- st (npm): affected all versions; fixed in 1.2.2\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-16224/ (Markdown: https://insights.sbomify.com/CVE-2017-16224/index.md)","id":"CVE-2017-16224","markdown":"https://insights.sbomify.com/CVE-2017-16224/index.md","name":"CVE-2017-16224","record":{"aliases":["GHSA-72fg-jqhx-c68p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js static file module","requires_auth":"none","summary":"An attacker can craft requests to redirect users to external domains when the module serves files from the root directory.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"st","vendor":"st_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"st is a module for serving static files. An attacker is able to craft a request that results in an HTTP 301 (redirect) to an entirely different domain. A request for: http://some.server.com//nodesecurity.org/%2e%2e would result in a 301 to //nodesecurity.org/%2e%2e which most browsers treat as a proper redirect as // is translated into the current schema being used. Mitigating factor: In order for this to work, st must be serving from the root of a server (/) rather than the typical sub directory (/static/) and the redirect URL will end with some form of URL encoded .. (\"%2e%2e\", \"%2e.\", \".%2e\").","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":true,"headline":"Open Redirect in st","id":"CVE-2017-16224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"open_redirect","year":"2017"},"n_packages":2,"n_references":1,"next":{"headline":"Github Token Leak in aegir","id":"CVE-2017-16225"},"packages":[{"ecosystem":"npm","fixed":["1.2.2"],"introduced":["0"],"last_affected":[],"package":"st","purl":null,"source":"GHSA-72fg-jqhx-c68p"},{"ecosystem":"npm","fixed":["1.2.2"],"introduced":["0"],"last_affected":[],"package":"st","purl":"pkg:npm/st","source":"GHSA-72fg-jqhx-c68p"}],"prev":{"headline":"Directory Traversal in nodeaaaaa","id":"CVE-2017-16223"},"products":["st 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 craft requests to redirect users to external domains when the module serves files from the root directory.","url":"https://insights.sbomify.com/CVE-2017-16224/"}