GHSA-88j4-pcx8-q4q3

Suggest an improvement
Source
https://github.com/advisories/GHSA-88j4-pcx8-q4q3
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/12/GHSA-88j4-pcx8-q4q3/GHSA-88j4-pcx8-q4q3.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-88j4-pcx8-q4q3
Aliases
Related
Published
2023-12-12T00:59:30Z
Modified
2025-01-14T12:12:27.917709Z
Severity
  • 6.7 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
Password Change Vulnerability
Details

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 | | 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 |

Database specific 
{
    "nvd_published_at": "2023-12-11T23:15:07Z",
    "cwe_ids": [
        "CWE-384"
    ],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2023-12-12T00:59:30Z"
}
References

Affected packages

npm / uptime-kuma

Package

Name
uptime-kuma
View open source insights on deps.dev
Purl
pkg:npm/uptime-kuma

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.23.9