CVE-2024-50355: Librenms/librenms Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-4m5r-w2rq-q54q
CVSS 7.2
CWE-79
Published
Advisory Summary

CVE-2024-50355 is a HIGH (CVSS 7.2) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Librenms/librenms libraries in the Packagist ecosystem. The issue involves librenms has a persistent xss from insecure input sanitization affects multiple endpoints. Remediation is available by upgrading affected packages to version 24.10.0.

CVE-2024-50355 at a Glance

CVE Identifier CVE-2024-50355
GHSA Identifier GHSA-4m5r-w2rq-q54q
Severity HIGH
CVSS v3.1 Base Score 7.2
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Librenms/librenms
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2024-50355

To remediate this vulnerability, upgrade all affected Librenms/librenms dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

librenms/librenms fixed: 24.10.0
Upgrade librenms/librenms to 24.10.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for librenms/librenms

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-50355, inspect your project dependencies for Librenms/librenms:

inspect dependencies for librenms/librenms

Analyze the terminal output to locate any version of Librenms/librenms in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 24.10.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Librenms/librenms, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://github.com/user-attachments/assets/a0cce15d-fa25-46cf-a16d-648b501724a4) 2.1. Go to manage user and choose Manage Access ![image](https://github.com/user-attachments/assets/079bd7a7-c153-4630-a59e-416bbbaf267b) 2.2. A pop-up will show ![image](https://github.com/user-attachments/assets/2fe15976-c25d-4ba5-a9c1-08cfaa5c1c5b) 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](https://github.com/user-attachments/assets/135093ba-d28c-4fe4-871d-950a2d521b01) 3.2. Once the device is down, there will be an alert in the Alerts Notifications ![image](https://github.com/user-attachments/assets/f32461be-aee2-43e7-ba50-977ed27754b4) 3.3. Hover over the Hostname will see a pop-up. ![image](https://github.com/user-attachments/assets/314eed99-1372-40e8-818f-4494679e476e) 4.1. The same can be trigger in the Alert History once hover over the Device field. ![image](https://github.com/user-attachments/assets/33dd2045-2c21-4305-a7a6-8c09101baf81) 5.1. The same can be trigger once hover over the Hostname field from the Event Log of the device. ![image](https://github.com/user-attachments/assets/a8a80dc7-4678-4334-a03a-e38d61e55e1c) 6.1. The same can be trigger in the Outages function in the Logs of the device. ![image](https://github.com/user-attachments/assets/b25d1c20-de6d-4c8d-bfab-59691b3faf1e) 7.1. In the Active Alerts of the device. ![image](https://github.com/user-attachments/assets/73571f83-56e2-4e6f-9af4-621df2a0ccdd) 8.2. In the Alert History of the device. ![image](https://github.com/user-attachments/assets/1fa4a86b-4469-4e09-a4d8-174529138199) 9.1. They can also be trigger in the dashboard. ![image](https://github.com/user-attachments/assets/0d3f3926-b41d-48d2-9212-cbd5692f6a9e) ![image](https://github.com/user-attachments/assets/6f36fc02-eae5-4a46-b6ba-f99a8d1db8a8) 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](https://github.com/user-attachments/assets/9ed7ebb1-4906-43f0-aa96-313fe722a533) ![image](https://github.com/user-attachments/assets/d7c57840-4431-4ccb-b688-e813c83ac20c) ### 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.

CVE-2024-50355 Affected Librenms/librenms Versions

1 component(s)
Fixed Versions:
24.10.0
Product / Package Ecosystem Affected Versions Fixed Version
librenms/librenms
Packagist
< 24.10.0
24.10.0

References

Frequently Asked Questions

What is CVE-2024-50355?
CVE-2024-50355 is a security vulnerability in Librenms/librenms involving LibreNMS has a Persistent XSS from Insecure Input Sanitization Affects Multiple Endpoints under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Librenms/librenms versions are affected?
Affected versions include releases prior to 24.10.0 across affected packages: librenms/librenms.
What version fixes CVE-2024-50355?
Upgrading to 24.10.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is librenms/librenms affected?
Yes, librenms/librenms is affected in releases prior to 24.10.0. Upgrade your dependency to 24.10.0 or later.
What is the CVSS score of CVE-2024-50355?
CVE-2024-50355 has a CVSS v3.1 base score of 7.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2024-50355?
CVE-2024-50355 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Packagist dependencies for CVE-2024-50355?
Run the dependency tree command: 'inspect dependencies for librenms/librenms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4m5r-w2rq-q54q",
  "modified" : "2024-11-15T20:49:55Z",
  "published" : "2024-11-15T15:41:38Z",
  "aliases" : [ "CVE-2024-50355" ],
  "summary" : "LibreNMS has a Persistent XSS from Insecure Input Sanitization Affects Multiple Endpoints",
  "details" : "### Summary\n\nThe application fail to sanitising inputs properly and rendering the code from user input to browser which allow an attacker to execute malicious javascript code.\n\n### Details\n\nUser 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.\n\n### PoC\n\n1. Use an Admin role user to change the Display Name of a device into the payload `<img src=\"x\" onerror=\"alert(document.cookie)\">`\n\n![image](https://github.com/user-attachments/assets/a0cce15d-fa25-46cf-a16d-648b501724a4)\n\n2.1. Go to manage user and choose Manage Access\n\n![image](https://github.com/user-attachments/assets/079bd7a7-c153-4630-a59e-416bbbaf267b)\n\n2.2. A pop-up will show\n\n![image](https://github.com/user-attachments/assets/2fe15976-c25d-4ba5-a9c1-08cfaa5c1c5b)\n\n3.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.\n\n![image](https://github.com/user-attachments/assets/135093ba-d28c-4fe4-871d-950a2d521b01)\n\n3.2. Once the device is down, there will be an alert in the Alerts Notifications\n\n![image](https://github.com/user-attachments/assets/f32461be-aee2-43e7-ba50-977ed27754b4)\n\n3.3. Hover over the Hostname will see a pop-up.\n\n![image](https://github.com/user-attachments/assets/314eed99-1372-40e8-818f-4494679e476e)\n\n4.1. The same can be trigger in the Alert History once hover over the Device field.\n\n![image](https://github.com/user-attachments/assets/33dd2045-2c21-4305-a7a6-8c09101baf81)\n\n5.1. The same can be trigger once hover over the Hostname field from the Event Log of the device.\n\n![image](https://github.com/user-attachments/assets/a8a80dc7-4678-4334-a03a-e38d61e55e1c)\n\n6.1. The same can be trigger in the Outages function in the Logs of the device.\n\n![image](https://github.com/user-attachments/assets/b25d1c20-de6d-4c8d-bfab-59691b3faf1e)\n\n7.1. In the Active Alerts of the device.\n\n![image](https://github.com/user-attachments/assets/73571f83-56e2-4e6f-9af4-621df2a0ccdd)\n\n8.2. In the Alert History of the device.\n\n![image](https://github.com/user-attachments/assets/1fa4a86b-4469-4e09-a4d8-174529138199)\n\n9.1. They can also be trigger in the dashboard.\n\n![image](https://github.com/user-attachments/assets/0d3f3926-b41d-48d2-9212-cbd5692f6a9e)\n\n![image](https://github.com/user-attachments/assets/6f36fc02-eae5-4a46-b6ba-f99a8d1db8a8)\n\n10.1. Also if change the payload into `<img src=\"x\" onerror=\"alert(document['cookie'])\">`, it can also be trigger in the Availability Map.\n\n![image](https://github.com/user-attachments/assets/9ed7ebb1-4906-43f0-aa96-313fe722a533)\n\n![image](https://github.com/user-attachments/assets/d7c57840-4431-4ccb-b688-e813c83ac20c)\n\n### Impact\n\nIt could allow authenticated users to execute arbitrary JavaScript code in the context of other users' sessions.\nImpacted users could have their accounts compromised, enabling the attacker to perform unauthorized actions on their behalf.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "librenms/librenms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "24.10.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 24.9.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/librenms/librenms/security/advisories/GHSA-4m5r-w2rq-q54q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-50355"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/librenms/librenms/commit/bb4731419b592867bf974dde525e536606a52976"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/librenms/librenms"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-11-15T15:41:38Z",
    "nvd_published_at" : "2024-11-15T16:15:36Z"
  }
}