Detection Guidance

This vulnerability can be detected by checking if device names in the Advantech WISE-DeviceOn Server (versions prior to 5.4) contain suspicious or malicious script tags, especially in the /rmm/v1/devices/name/{agent_id} endpoint. Since it requires authenticated access to rename devices, you can audit device names for injected scripts. Commands to detect this might include querying the device names via API calls or database queries and searching for HTML or JavaScript code patterns. For example, using curl to fetch device names and grep to find script tags: curl -s -H "Authorization: Bearer <token>" https://<deviceon-server>/rmm/v1/devices/name/<agent_id> | grep -i '<script>' or querying the database for device names containing suspicious characters. However, no specific commands are provided in the resources. [1]

Useful 0 Not Useful 0

Executive Summary

This vulnerability is a stored cross-site scripting (XSS) issue in Advantech WISE-DeviceOn Server versions prior to 5.4. It occurs in the /rmm/v1/devices/name/{agent_id} endpoint where an authenticated user can rename a device. The new device name is stored and later displayed without proper HTML sanitation, allowing an attacker to inject malicious scripts. These scripts execute in the browsers of users who view or interact with the affected device, potentially leading to session compromise and unauthorized actions.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to session compromise and unauthorized actions by attackers. If a malicious script is injected into a device name, it can execute in the browser of users who view the device, potentially allowing attackers to hijack user sessions or perform actions on behalf of the victim without their consent.

Useful 0 Not Useful 0

Mitigation Strategies

The immediate mitigation step is to update Advantech WISE-DeviceOn Server to version 5.4 or later, where this stored XSS vulnerability has been fixed by properly sanitizing the new_name input. Additionally, restrict device renaming privileges to trusted users only and monitor device names for suspicious content. Applying proper input validation and output encoding on the server side is essential, but the primary recommendation is to upgrade to the fixed version. [1]

Useful 0 Not Useful 0