Skip to content

LibreNMS uses Improper Sanitization on Service template name leads to Stored XSS

High severity GitHub Reviewed Published Apr 20, 2024 in librenms/librenms • Updated Apr 23, 2024

Package

composer librenms/librenms (Composer)

Affected versions

< 24.4.0

Patched versions

24.4.0

Description

Summary

There is improper sanitization on Service template name which is reflecting in delete button onclick event. This value can be modified and crafted as any other javascript code.

Vulnerable Code

https://github.com/librenms/librenms/blob/a61c11db7e8ef6a437ab55741658be2be7d14d34/app/Http/Controllers/ServiceTemplateController.php#L67C23-L67C23

Above is vulnerable code line which needs to be properly sanitized

PoC

  1. Go to /services/templates
  2. Enter name as testing', '14', 'http://172.105.62.194:8000/services/templates/14');alert(1);//
  3. Submit it and try to delete it, you will see popup

If you inspect element on delete button, you will notice this:-
Screenshot 2023-11-23 at 9 30 24 PM

Impact

Cross site scripting can lead to cookie stealing or an attacker can execute any other feature using this feature.

References

@murrant murrant published to librenms/librenms Apr 20, 2024
Published to the GitHub Advisory Database Apr 22, 2024
Reviewed Apr 22, 2024
Published by the National Vulnerability Database Apr 22, 2024
Last updated Apr 23, 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
High
Privileges required
Low
User interaction
Required
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:H/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2024-32479

GHSA ID

GHSA-72m9-7c8x-pmmw

Source code

Credits

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