Amir Zaltzman

A flaw exists that allows a logged-in attacker to execute code on the system remotely. This is achieved by injecting malicious input into the `username` and/or `password` fields within the restore action located at the `/api/V1` endpoint.

A flaw exists that allows a logged-in attacker to execute code on a system remotely. This is achieved by altering harmful input within the URL of the MBird SMS service and/or code through the utility path. This input is then processed during system configuration, resulting in remote code execution. The vulnerability is an OS command injection.

A flaw exists that allows a logged-in attacker to execute code remotely on a system. This is achieved by injecting malicious input into requests sent to the `/templates` route. The issue is an OS command injection.

An operating system command injection issue exists that allows an authenticated attacker to execute code remotely. This is achieved by injecting malicious input into the map filename field during the map upload action of the parameters route.

A flaw exists that allows a logged-in attacker to execute code on a system remotely. This is achieved by injecting malicious input into the `devices` field within the firmware update action. The injection leads to remote code execution.

An authentication bypass allows attackers to circumvent the authentication requirement and achieve pre-authenticated code execution on the system. The flaw allows remote exploitation over the network without requiring prior access or user interaction.

An operating system command injection issue exists, allowing an authenticated attacker to execute code remotely. This is achieved by submitting crafted input to the firmware update route. The issue affects systems running the vulnerable software.

An unauthenticated attacker can execute commands on the system remotely. This is possible by sending a specially crafted request to the libraries installation route and injecting malicious input into the request body. The application improperly processes requests, allowing for remote code execution (RCE).

A flaw exists that allows a logged-in attacker to execute code remotely on a system. This is possible by injecting malicious input into the `devices` field within the firmware update apply action. The issue is an OS command injection.

A flaw exists that allows a logged-in attacker to execute code remotely on a system. This is achieved by injecting harmful input into OpenSSL argument fields within requests sent to the utility route. The vulnerability leads to remote code execution.

A flaw exists that allows an authentication bypass due to improper handling of return values from the authentication routine. The software processes an unexpected return value as legitimate, bypassing authentication controls.

A flaw exists that allows a logged-in attacker to execute code remotely on a system. This is possible by injecting malicious input into the `devices` field when accessing the `/get setup` API endpoint. This results in remote code execution.

An OS command injection issue exists that allows a logged-in attacker to execute code remotely on the system. This is achieved by submitting crafted input to the restore route. The `restore` route is susceptible to command injection due to improper input validation. The vulnerable parameter is not specified.

An operating system command injection issue exists in XWEB Pro. A successful exploit allows an authenticated attacker to execute code remotely on the system by providing a manipulated firmware update file through the firmware update path. The vulnerable component is the firmware update route. The vulnerable parameter is the firmware update file.

An OS command injection issue exists, allowing an authenticated attacker to execute code remotely. This is achieved by providing malicious input through the device hostname configuration during system setup. The system processes this input, leading to remote code execution.

A stack-based buffer overflow exists in an API route of XWEB Pro. This allows unauthenticated attackers to cause stack corruption and program termination. The vulnerable API route is not specified.

An arbitrary file-read issue exists in XWEB Pro, potentially allowing unauthenticated attackers to read arbitrary files on the system. This could lead to a denial-of-service attack.

A flaw exists that allows a logged-in attacker to execute code on the system. This is possible by submitting crafted input into the username field of the import preconfiguration action via the API V1 route. The affected API endpoint is '/api/V1'. The vulnerable parameter is `username`.

An operating system command injection issue exists in XWEB Pro, allowing an authenticated attacker to execute code remotely on the system. This is achieved by providing a manipulated template file to the `/devices` route. The `template file` is the source of the injection.

A flaw exists that allows a logged-in attacker to execute code on the system remotely. This is achieved by configuring a specially crafted LCD state, which is then processed during system setup. The vulnerability is an OS command injection.