Skip to content

LibreNMS has a Persistent XSS from Insecure Input Sanitization Affects Multiple Endpoints

High severity GitHub Reviewed Published Nov 15, 2024 in librenms/librenms • Updated Nov 15, 2024

Package

composer librenms/librenms (Composer)

Affected versions

<= 24.9.0

Patched versions

24.10.0

Description

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

  1. Use an Admin role user to change the Display Name of a device into the payload <img src="x" onerror="alert(document.cookie)">

image

2.1. Go to manage user and choose Manage Access

image

2.2. A pop-up will show

image

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.

image

3.2. Once the device is down, there will be an alert in the Alerts Notifications

image

3.3. Hover over the Hostname will see a pop-up.

image

4.1. The same can be trigger in the Alert History once hover over the Device field.

image

5.1. The same can be trigger once hover over the Hostname field from the Event Log of the device.

image

6.1. The same can be trigger in the Outages function in the Logs of the device.

image

7.1. In the Active Alerts of the device.

image

8.2. In the Alert History of the device.

image

9.1. They can also be trigger in the dashboard.

image

image

10.1. Also if change the payload into <img src="x" onerror="alert(document['cookie'])">, it can also be trigger in the Availability Map.

image

image

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

@murrant murrant published to librenms/librenms Nov 15, 2024
Published to the GitHub Advisory Database Nov 15, 2024
Reviewed Nov 15, 2024
Published by the National Vulnerability Database Nov 15, 2024
Last updated Nov 15, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Weaknesses

CVE ID

CVE-2024-50355

GHSA ID

GHSA-4m5r-w2rq-q54q

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.