Omnitaint

The issue is related to Arbitrary Code Execution due to missing sanitization of input passed to the `Function` constructor. This allows for potential code execution with unintended consequences. No information is provided about the estimated number of potentially affected devices worldwide or real-world incidents where this issue was exploited.

The issue is related to Arbitrary Command Injection due to missing sanitization of input that potentially flows into the `child process.exec()` function. This affects a FontForge wrapper used for conversion between different font formats, including TTF, WOFF, and OTF.

The issue arises from the usage of the Function constructor without input sanitization in the package's exported constructor function. If attacker-controlled user input is given to the `format` option, it is possible for an attacker to execute arbitrary JavaScript code on the host.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given to the `getCredential` function. This is due to the use of the `child process` `exec` function without input sanitization, which can lead to command execution.

The issue arises when attacker-controlled user input is given to the `scroll` function, allowing an attacker to execute arbitrary commands due to the use of the `child process` `exec` function without input sanitization.

The issue arises when attacker-controlled user input is given to the kill function, allowing an attacker to execute arbitrary commands due to the use of the child process exec function without input sanitization.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given to the `trimvideo` function. This is due to the use of the `child process` `exec` function without input sanitization, which can lead to command execution.

The issue arises when attacker-controlled user input is given to the `say` function, allowing an attacker to execute arbitrary commands due to the use of the `child process` `exec` function without input sanitization.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is provided. This is caused by the use of the child process exec function without proper input sanitization.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given to the `stat` function of the package on certain operating systems. This is due to the use of the `child process` `exec` function without input sanitization.

[Content removed]

The issue arises when attacker-controlled user input is given to the `kill` function, allowing an attacker to execute arbitrary commands due to the use of the `child process` `exec` function without input sanitization.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given to the `killProcess` function. This is due to the use of the `child process` `exec` function without input sanitization.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given to the `killByPort()` function. This is due to the use of the `child process` `exec` function without input sanitization.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given. This is due to the use of the child process exec function without input sanitization. For example, running a proof of concept will cause the command `touch success` to be executed, leading to the creation of a file called `success`.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given. This is due to the use of the child process exec function without input sanitization. For example, running a proof of concept will cause the command `touch success` to be executed, leading to the creation of a file called `success`.

The issue allows an attacker to execute arbitrary commands if attacker-controlled user input is given. This is due to the use of the child process exec function without input sanitization in the index.js file.

The issue affects the ps-kill package, where an attacker can execute arbitrary commands if attacker-controlled user input is given to the `kill` function. This is due to the use of the `child process` `exec` function without input sanitization in the `index.js` file. A proof of concept (PoC) demonstrates this vulnerability by using the `kill` function with a malicious input, such as `$(touch success)`, which can lead to arbitrary command execution.