Headline
GHSA-4m5r-w2rq-q54q: LibreNMS has a Persistent XSS from Insecure Input Sanitization Affects Multiple Endpoints
Summary
The application fail to sanitising inputs properly and rendering the code from user input to browser which allow an attacker to execute malicious javascript code.
Details
User with Admin role can edit the Display Name of a device, the application did not properly sanitize the user input in the device Display Name, if java script code is inside the name of the device Display Name, its can be trigger from different sources.
PoC
- Use an Admin role user to change the Display Name of a device into the payload
<img src="x" onerror="alert(document.cookie)">
2.1. Go to manage user and choose Manage Access
2.2. A pop-up will show
3.1. Create a new Alert Rule where it will check if the device is up or down by using ICMP and then add the rule to the device.
3.2. Once the device is down, there will be an alert in the Alerts Notifications
3.3. Hover over the Hostname will see a pop-up.
4.1. The same can be trigger in the Alert History once hover over the Device field.
5.1. The same can be trigger once hover over the Hostname field from the Event Log of the device.
6.1. The same can be trigger in the Outages function in the Logs of the device.
7.1. In the Active Alerts of the device.
8.2. In the Alert History of the device.
9.1. They can also be trigger in the dashboard.
10.1. Also if change the payload into <img src="x" onerror="alert(document['cookie'])">, it can also be trigger in the Availability Map.
Impact
It could allow authenticated users to execute arbitrary JavaScript code in the context of other users’ sessions. Impacted users could have their accounts compromised, enabling the attacker to perform unauthorized actions on their behalf.
Summary
The application fail to sanitising inputs properly and rendering the code from user input to browser which allow an attacker to execute malicious javascript code.
Details
User with Admin role can edit the Display Name of a device, the application did not properly sanitize the user input in the device Display Name, if java script code is inside the name of the device Display Name, its can be trigger from different sources.
PoC
- Use an Admin role user to change the Display Name of a device into the payload <img src="x" onerror="alert(document.cookie)">
2.1. Go to manage user and choose Manage Access
2.2. A pop-up will show
3.1. Create a new Alert Rule where it will check if the device is up or down by using ICMP and then add the rule to the device.
3.2. Once the device is down, there will be an alert in the Alerts Notifications
3.3. Hover over the Hostname will see a pop-up.
4.1. The same can be trigger in the Alert History once hover over the Device field.
5.1. The same can be trigger once hover over the Hostname field from the Event Log of the device.
6.1. The same can be trigger in the Outages function in the Logs of the device.
7.1. In the Active Alerts of the device.
8.2. In the Alert History of the device.
9.1. They can also be trigger in the dashboard.
10.1. Also if change the payload into <img src="x" onerror="alert(document[‘cookie’])">, it can also be trigger in the Availability Map.
Impact
It could allow authenticated users to execute arbitrary JavaScript code in the context of other users’ sessions.
Impacted users could have their accounts compromised, enabling the attacker to perform unauthorized actions on their behalf.
References
- GHSA-4m5r-w2rq-q54q
- librenms/librenms@bb47314