Command Injection in killport (CVE-2021-23360)
Summary
Command injection in killport (CVE-2021-23360). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.2 or later.
Original description
The description as published by the source.
This affects the package killport before 1.0.2. If (attacker-controlled) user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization. Running this PoC will cause the command touch success to be executed, leading to the creation of a file called success.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-23360 has been found in killport.
Successful exploitation can lead to full system takeover.
What to do: upgrade killport to 1.0.2 or later.
If unsure, ask your IT team or search "killport CVE-2021-23360" on the vendor's site.
CVE-2021-23360 (killport) — CWE-77
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-77) exists in killport.
Check the vendor advisory for the affected versions of killport.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'killport' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'killport' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
killportを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade killport to 1.0.2ステージング環境で 1.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web snyk.io