Stored XSS via unescaped device display name
Published Jan 16, 2025 · Updated Feb 12, 2025
Stored XSS in LibreNMS before 24.12.0 allows remote authenticated users to run scripts in another user's browser via a device display name. Table controllers pass the stored display value through legacy Url::deviceLink overlib HTML generation, which does not escape it safely for page output. Device-edit access is required to save the payload, and execution requires another user to open the affected device logs view and hover over its type link.
Summary
What happened
Stored XSS in LibreNMS before 24.12.0 allows remote authenticated users to run scripts in another user's browser via a device display name. Table controllers pass the stored display value through legacy Url::deviceLink overlib HTML generation, which does not escape it safely for page output. Device-edit access is required to save the payload, and execution requires another user to open the affected device logs view and hover over its type link.
The record
- CVE
- CVE-2024-56144
- Published
- Jan 16, 2025
- Updated
- Feb 12, 2025
- Vendor
- LibreNMS
- Product
- LibreNMS
- Classifications
- CWE-79, CAPEC-63, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 16, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 24.12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-2f4w-6mc7-4w78 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo