{"answers":{"affected":"2 open source packages ship an affected version, including kill-port-process. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15609 in the wild and no public exploit code.","fix":"Upgrade kill-port-process to 2.2.0 or later.","what":"CVE-2019-15609 is a critical vulnerability in kill-port-process, published on 28 Feb 2020."},"fix_prompt":"Check this codebase for CVE-2019-15609 and fix it if it is affected.\n\nWhat it is: CVE-2019-15609 is a critical vulnerability in kill-port-process, published on 28 Feb 2020. \nExploitation: There is no known exploitation of CVE-2019-15609 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kill-port-process (npm): affected all versions; fixed in 2.2.0\n- kill-port-process (npm): affected all versions; fixed in 2.2.0\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-2019-15609/ (Markdown: https://insights.sbomify.com/CVE-2019-15609/index.md)","id":"CVE-2019-15609","markdown":"https://insights.sbomify.com/CVE-2019-15609/index.md","name":"CVE-2019-15609","record":{"aliases":["GHSA-xp4x-j9vh-c3wf"],"analysis":null,"analysis_generated_by":null,"assigner":"hackerone","cpe":[{"product":"kill-port-process","vendor":"kill-port-process_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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":"The kill-port-process package version \u003c 2.2.0 is vulnerable to a Command Injection vulnerability.","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":"OS Command Injection and Command Injection in kill-port-process","id":"CVE-2019-15609","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Missing authorization in Nextcloud Circles","id":"CVE-2019-15610"},"packages":[{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"kill-port-process","purl":null,"source":"GHSA-xp4x-j9vh-c3wf"},{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"kill-port-process","purl":"pkg:npm/kill-port-process","source":"GHSA-xp4x-j9vh-c3wf"}],"prev":{"headline":"TOCTOU Race Condition in Yarn","id":"CVE-2019-15608"},"products":["kill-port-process"],"published":"2020-02-28","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":null,"url":"https://insights.sbomify.com/CVE-2019-15609/"}