Arbitrary command execution via process-name injection
Published Aug 29, 2022 · Updated Sep 17, 2024
Code injection in @pendo324/get-process-by-name allows remote attackers to execute arbitrary commands through a crafted process name. The getProcessByName function inserts executableName directly into a cmd.exe tasklist command without escaping shell metacharacters. Exploitation requires a consuming application to pass attacker-controlled input to the function, allowing commands to run with that application's privileges.
Summary
What happened
Code injection in @pendo324/get-process-by-name allows remote attackers to execute arbitrary commands through a crafted process name. The getProcessByName function inserts executableName directly into a cmd.exe tasklist command without escaping shell metacharacters. Exploitation requires a consuming application to pass attacker-controlled input to the function, allowing commands to run with that application's privileges.
The record
- CVE
- CVE-2022-25644
- Published
- Aug 29, 2022
- Updated
- Sep 17, 2024
- Vendor
- pendo324
- Product
- @pendo324/get-process-by-name
- Classifications
- CWE-94, T1059.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 getProcessByName command-injection 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