{"vuln_id":"GHSA-g9v2-wqcj-j99g","aliases":["CVE-2023-44400"],"description":"Persistentent User Sessions ","published_at":"2023-10-09T12:49:48Z","modified_at":"2023-10-09T15:05:06Z","first_seen_at":"2026-11-22T13:40:14.917924Z","severity":"medium","severity_source":"ghsa","cvss_score":6.7,"cvss_vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","cwe":["CWE-565","CWE-602","CWE-784"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":null,"epss_percentile":null,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://github.com/advisories/GHSA-g9v2-wqcj-j99g"},"matched_alias":null,"items":[{"id":12019,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-23q2-5gf8-gjpp: Enabling Authentication does not close all logged in socket connections immediately","summary":"Enabling Authentication does not close all logged in socket connections immediately \n\n### Summary\r\nThis is basically [GHSA-88j4-pcx8-q4q](https://github.com/louislam/uptime-kuma/security/advisories/GHSA-88j4-pcx8-q4q3) but instead of changing passwords, when enabling authentication.\r\n\r\n### PoC\r\n- Open Uptime Kuma with authentication disabled\r\n- Enable authentication using another window\r\n- Access the platform using the previously logged-in window\r\n- Note that access (read-write) remains despite the enabled authentication\r\n- Expected behaviour:\r\n  - After enabling authentication, all previously connected sessions should be invalidated, requiring users to log in.\r\n- Actual behaviour:\r\n  - The system retains sessions and never logs out users unless explicitly done by clicking logout or refreshing the page.\r\n\r\n### Impact\r\nSee [GHSA-g9v2-wqcj-j99g](https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g) and [GHSA-88j4-pcx8-q4q](https://github.com/louislam/uptime-kuma/security/advisories/GHSA-88j4-pcx8-q4q3)\r\n\r\nTBH this is quite a niche edge case, so I don't know if this even warrants a security report.  \r\n\n\nAffected packages: docker:louislam/uptime-kuma, npm:louislam/uptime-kuma\nPatched: louislam/uptime-kuma 1.23.12, louislam/uptime-kuma 1.23.12","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-23q2-5gf8-gjpp","published_at":"2024-04-19T03:24:03Z","updated_at":"2024-04-19T03:24:03Z","fetched_at":"2026-11-22T13:40:14.883736Z","severity":"medium","cvss_score":6.7,"epss":null,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"GHSA-23q2-5gf8-gjpp","vuln_ids":["CVE-2023-44400","CVE-2023-49804","GHSA-23Q2-5GF8-GJPP","GHSA-88J4-PCX8-Q4Q3","GHSA-G9V2-WQCJ-J99G"],"tags":["repo-advisory","docker","npm","security","repo:louislam/uptime-kuma"],"cluster_id":11324,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12019","html":"https://vulnwatch.ve1ve2.com/item/12019"}},{"id":12021,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-88j4-pcx8-q4q3 / CVE-2023-49804: Changing Password does not close all logged in socket connections immediately","summary":"Changing Password does not close all logged in socket connections immediately\n\n> [!WARNING]\r\n> As is written in our [**security policy**](https://github.com/louislam/uptime-kuma/security/policy), please **DON'T REPORT SECURITY ISSUES TO OUR PUBLIC ISSUE TRACKER**\r\n> Posting as [an advisory](https://github.com/louislam/uptime-kuma/security/advisories/new) and then create a [`security`-issue without details](https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md) allows us to privately come up with a securty fix without having to scramble and potentialy miss/break something.\r\n> These steps were violated in this case, as the issue was first raised as a `bug`-report in issue #4188 [^1]\r\n\r\n## Overview:\r\n\r\nA moderate security vulnerability has been identified in Uptime Kuma platform that poses a significant threat to the confidentiality and integrity of user accounts.  \r\nWhen a user changes their login password in Uptime Kuma, a previously logged-in user retains access without being logged out.\r\nThis behaviour persists consistently, even after system restarts or browser restarts.\r\nThis vulnerability allows unauthorized access to user accounts, compromising the security of sensitive information.\r\n\r\nThe same vulnerability was partially fixed in https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g but logging existing users out of their accounts was forgotten.\r\n\r\n## Impact:\r\n\r\nThe impact of this vulnerability is moderate, as it enables attackers or unauthorized individuals to maintain access to user accounts even after the account password has been changed. This can lead to unauthorized data access, manipulation, or compromise of user accounts, posing a threat to the integrity and confidentiality of Uptime Kuma.\r\nA better impact-analysis is included in https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g\r\n\r\n## PoC\r\n\r\n- Change the password for a user account\r\n- Access the platform using the previously logged-in account without logging out\r\n- Note that access (read-write) remains despite the password change \r\n- Expected behaviour:  \r\n   After changing the password for a user account, all previously logged-in sessions should be invalidated, requiring users to log in again with the updated credentials.\r\n- Actual behaviour:  \r\n  The system retains sessions and never logs out users unless explicitly done by clicking logout.\r\n\r\n## Remediation:\r\n\r\nTo mitigate the risks associated with this vulnerability, we made the server emit a `refresh` event (clients handle this by reloading) and then disconnecting all clients except the one initiating the password change.\r\n\r\nIt is recommended to Update Uptime Kuma to `>= 1.23.9`. \r\n\r\n## Timeline:\r\n\r\n|Date|Event|\r\n|--|--|\r\n|2023-12-07 14:35 UTC| @manoonabbasi discovered and posts this information as a `bug`-report in issue #4188 [^1] into our **public issue tracker**, which is [**against our security policy**](https://github.com/louislam/uptime-kuma/security/policy) |\r\n| 2023-12-07 16:50 UTC | The Uptime Kuma t\n\nAffected packages: docker:louislam/dockge, docker:louislam/uptime-kuma, npm:louislam/uptime-kuma\nPatched: louislam/uptime-kuma 1.23.9, louislam/uptime-kuma 1.23.9, louislam/dockge 1.3.3","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-88j4-pcx8-q4q3","published_at":"2023-12-10T17:56:02Z","updated_at":"2023-12-11T17:53:24Z","fetched_at":"2026-11-22T13:40:14.883737Z","severity":"medium","cvss_score":6.7,"epss":0.00263,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"CVE-2023-49804","vuln_ids":["CVE-2023-44400","CVE-2023-49804","GHSA-88J4-PCX8-Q4Q3","GHSA-G9V2-WQCJ-J99G"],"tags":["repo-advisory","docker","npm","security","repo:louislam/uptime-kuma"],"cluster_id":11325,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12021","html":"https://vulnwatch.ve1ve2.com/item/12021"}},{"id":12024,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-g9v2-wqcj-j99g / CVE-2023-44400: Persistentent User Sessions","summary":"Persistentent User Sessions \n\n# Summary\r\n\r\nAttackers with access to a users' device can gain persistent account access.\r\nThis is caused by missing verification of Session Tokens after password changes and/or elapsed inactivity-periods.\r\n\r\n# Details\r\n\r\n`uptime-kuma` sets JWT tokens for users after successful authentication.\r\n\r\nThese tokens have the following design flaws:\r\n- After successful login, a JWT token and it is stored in `sessionStorage` or `localStorage`. \r\n  Which of the two is decided based on the `Remember Me` button. \r\n  The users' token is valid without any time limitation, even after long periods of inactivity. \r\n  This increases the risk of session hijacking if, for example, a user forgets to log off and leaves the PC.\r\n- sessions are only deleted on the client side after a user loggs out, meaning a local attacker could reuse said token with deep system access over the browser\r\n- If a user changes a password\r\n  - any previously logged in clients are not logged out\r\n  - previously issued tokens remained valid forever\r\n\r\nThese flaws allow user cookies to remain valid even after changing passwords or being inactive, posing a high security risk.\r\n\r\n# POC\r\n### Password resets not deactivating cookies\r\n- Log in.\r\n- Note the user cookie.\r\n- Change your password.\r\n- Attempt to log in again with the same cookie.\r\n- The cookie remains valid despite the password change.\r\n\r\n### Inactivity not deactivating sessions\r\n In testing, even after a period of over a day of inactivity, the session was still valid\r\n\r\n# Impact\r\n\r\nAnother person with local access to the device could take over the session permanently, even after hours of previous inactivity or a password change.\r\nSuch activity would not be obvious to the user (see https://github.com/louislam/uptime-kuma/issues/3481 if you want to help with this).\r\n\r\nWith this gained account access, an attacker can cause:\r\n\r\n## confidentially loss\r\n- monitors (including private ones not shared on public status pages)\r\n- notification providers \r\n- settings like `api-keys` (only used for accessing `/metrics`)\r\n- settings like secrets like the `Steam API Key`\r\n- maintenance periods\r\n\r\n## availability loss \r\n\r\n- by creating a lot of monitors and setting the retention policy very high leading to degraded database performance or out of storage\r\n- by creating a lot of `HTTP(s) - Browser Engine (Chrome/Chromium) (Beta)` leading to RAM exhaustion\r\n\r\n## integrity loss\r\n- by the attacker deleting a monitor\r\n- by the attacker deleting a monitor's history\r\n- by the atacker changing the meaning of a monitor (changing where it points)\r\n\r\n## scope creep\r\nIf operated in some restricted network, access to monitors may provide the ability to change the scope of the attack to a different piece of infrastructure, for example via SQL commands to a database server.\r\nWe have not classified this as `changed scope` because credentials stored in the application for accessing other systems are existing valid paths across the trust boundary, and the user should be \n\nAffected packages: docker:louislam/uptime-kuma, node.js:louislam/uptime-kuma\nPatched: louislam/uptime-kuma v1.23.3, louislam/uptime-kuma v1.23.3","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g","published_at":"2023-10-09T12:49:48Z","updated_at":"2023-10-09T15:05:06Z","fetched_at":"2026-11-22T13:40:14.883739Z","severity":"medium","cvss_score":6.7,"epss":0.00282,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"louislam/uptime-kuma","vuln_id":"CVE-2023-44400","vuln_ids":["CVE-2023-44400","GHSA-G9V2-WQCJ-J99G"],"tags":["repo-advisory","docker","node.js","CWE-565","CWE-602","CWE-784","security","repo:louislam/uptime-kuma"],"cluster_id":11326,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12024","html":"https://vulnwatch.ve1ve2.com/item/12024"}}]}