-= Per source details. Do not edit below this line.=- Source: amazon-inspector (da8762d3a240cbf5a33e4b613b2ea601d5515824da362b82eed4b5095baa7b8c) The package kill-port was found to contain malicious code. Source: ghsa-malware (12e6ea3a28f8e792e2cac11bd7aa1651eed2f77b6468a8d9aa435...
Product
npm kill-port vulnerabilities
2 published CVES affecting npm kill-port, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 2
- Critical
- 0
- High
- 1
- Medium
- 0
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Latest npm kill-port CVEs
Newest publication first
-
Unknown
-
HighCVSS 8.1 EPSS 1.9%
If an attacker can control the port, which in itself is a very sensitive value, they can inject arbitrary OS commands due to the usage of the exec function in a third-party module kill-port < 1.3.2.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.