CVE-2023-49804: Uptime Kuma Password Change Vulnerability

First published: Mon Dec 11 2023(Updated: )

## Overview: A moderate security vulnerability has been identified in Uptime Kuma platform that poses a significant threat to the confidentiality and integrity of user accounts. When a user changes their login password in Uptime Kuma, a previously logged-in user retains access without being logged out. This behaviour persists consistently, even after system restarts or browser restarts. This vulnerability allows unauthorized access to user accounts, compromising the security of sensitive information. The 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. ## Impact: The 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. A better impact-analysis is included in https://github.com/louislam/uptime-kuma/security/advisories/GHSA-g9v2-wqcj-j99g ## PoC - Change the password for a user account - Access the platform using the previously logged-in account without logging out - Note that access (read-write) remains despite the password change - Expected behaviour: 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. - Actual behaviour: The system retains sessions and never logs out users unless explicitly done by clicking logout. ## Remediation: To 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. It is recommended to Update Uptime Kuma to `>= 1.23.9`. ## Timeline: |Date|Event| |--|--| |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) | | 2023-12-07 16:50 UTC | The Uptime Kuma team deleted the post in our issue tracker | | 2023-12-10 18:10 UTC | Uptime Kuma team released patch and this Advisory | [^1]: deleted to prevent the spread of this vulnerability without there being a fix available

Credit: security-advisories@github.com

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• collector/github-advisory-latest
• alias/GHSA-88j4-pcx8-q4q3
• alias/CVE-2023-49804
• collector/github-advisory
• agent/type
• agent/first-publish-date
• agent/weakness
• agent/references
• agent/remedy
• agent/severity
• agent/title
• agent/description
• agent/event
• collector/mitre-cve
• source/MITRE
• agent/last-modified-date
• agent/trending
• agent/source
• agent/author
• agent/tags
• agent/softwarecombine
• collector/nvd-api
• agent/software-canonical-lookup-request
• collector/nvd-cve
• package-manager/npm
• vendor/dockge.kuma
• canonical/docke.kuma
• vendor/uptime.kuma
• canonical/uptime kuma