{"answers":{"affected":"2 open source packages ship an affected version, including apex-publish-static-files. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16462 in the wild and no public exploit code.","fix":"Upgrade apex-publish-static-files to 2.0.1 or later.","what":"CVE-2018-16462 is a critical command injection vulnerability in apex-publish-static-files, published on 30 Oct 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-2018-16462 and fix it if it is affected.\n\nWhat it is: CVE-2018-16462 is a critical command injection vulnerability in apex-publish-static-files, published on 30 Oct 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-2018-16462 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- apex-publish-static-files (npm): affected all versions; fixed in 2.0.1\n- apex-publish-static-files (npm): affected all versions; fixed in 2.0.1\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-16462/ (Markdown: https://insights.sbomify.com/CVE-2018-16462/index.md)","id":"CVE-2018-16462","markdown":"https://insights.sbomify.com/CVE-2018-16462/index.md","name":"CVE-2018-16462","record":{"aliases":["GHSA-9jm3-5835-537m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm static file publisher","requires_auth":"none","summary":"Attackers can execute arbitrary shell commands via malicious arguments in the apex-publish-static-files npm module.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"apex-publish-static-files","vendor":"apex-publish-static-files_project"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"A command injection vulnerability in the apex-publish-static-files npm module version \u003c2.0.1 which allows arbitrary shell command execution through a maliciously crafted argument.","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":"Command Injection in apex-publish-static-files","id":"CVE-2018-16462","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Auth bypass in Nextcloud Server","id":"CVE-2018-16463"},"packages":[{"ecosystem":"npm","fixed":["2.0.1"],"introduced":["0"],"last_affected":[],"package":"apex-publish-static-files","purl":null,"source":"GHSA-9jm3-5835-537m"},{"ecosystem":"npm","fixed":["2.0.1"],"introduced":["0"],"last_affected":[],"package":"apex-publish-static-files","purl":"pkg:npm/apex-publish-static-files","source":"GHSA-9jm3-5835-537m"}],"prev":{"headline":"Command Injection in libnmap","id":"CVE-2018-16461"},"products":["apex-publish-static-files"],"published":"2018-10-30","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":["n/a"]},"summary":"Attackers can execute arbitrary shell commands via malicious arguments in the apex-publish-static-files npm module.","url":"https://insights.sbomify.com/CVE-2018-16462/"}