Summary
The Command Sender UI uses an unsafe eval() function on array-like command parameters, which allows a user-supplied payload to execute in the browser when sending a command. This creates a self-XSS risk because an attacker can trigger their own script execution in the victim’s session, if allowed to influence the array parameter input, for example via phishing. If successful, an attacker may read or modify data in the authenticated browser context, including session tokens in local storage.
Details
The unsafe eval() usage on user-supplied ARRAY parameters happens in convertToValue method in CommandSender.vue
PoC
- Using a drop-down form, choose any command that supports ARRAY parameters,
- Inside square brackets “[…]” place a JavaScript code to be executed
- Send command to CmdTlmServer using dedicated “Send” button
- Observe JavaScript code being executed in the current browser session context
Below example uses INST ARYCMD to execute simple JavaScript code snippet alert(“XSS”).


Impact
Local JavaScript execution in the user's browser
References
Summary
The Command Sender UI uses an unsafe
eval()function on array-like command parameters, which allows a user-supplied payload to execute in the browser when sending a command. This creates a self-XSS risk because an attacker can trigger their own script execution in the victim’s session, if allowed to influence the array parameter input, for example via phishing. If successful, an attacker may read or modify data in the authenticated browser context, including session tokens in local storage.Details
The unsafe
eval()usage on user-supplied ARRAY parameters happens inconvertToValuemethod in CommandSender.vuePoC
Below example uses

INST ARYCMDto execute simple JavaScript code snippetalert(“XSS”).Impact
Local JavaScript execution in the user's browser
References