Arbitrary command execution via unsanitized process name
Published Mar 15, 2021 · Updated Sep 16, 2024
Command injection in rwolf449 kill-process-by-name 1.0.5 and earlier allows remote attackers to execute arbitrary commands. The exported function passes its process-name argument to child_process.exec in index.js without sanitizing shell metacharacters. Exploitation requires a consuming application to pass attacker-controlled input to the library, after which commands run with the application's OS privileges.
Summary
What happened
Command injection in rwolf449 kill-process-by-name 1.0.5 and earlier allows remote attackers to execute arbitrary commands. The exported function passes its process-name argument to child_process.exec in index.js without sanitizing shell metacharacters. Exploitation requires a consuming application to pass attacker-controlled input to the library, after which commands run with the application's OS privileges.
The record
- CVE
- CVE-2021-23356
- Published
- Mar 15, 2021
- Updated
- Sep 16, 2024
- Vendor
- rwolf449
- Product
- kill-process-by-name
- Classifications
- CWE-77, CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 15, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <unspecified
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Snyk shell-substitution proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo