Is CVE-2023-49804 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2023-49804 being exploited in the wild.

How severe is CVE-2023-49804?

Low severity, with a CVSS score of 3.1, published 12 December 2023.

Which products and versions are affected?

uptime-kuma (npm) SEMVER:introduced=0,fixed=1.23.9.

Is there a fix for CVE-2023-49804?

Yes. uptime-kuma (npm): upgrade to 1.23.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2023-49804 attacked?

It is attacked with local access or from the adjacent network, in a web application.

Am I affected by CVE-2023-49804?

Check whether you run uptime-kuma (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2023-49804: Uptime Kuma session persistence after password change

CVE-2023-49804 · Severity: low · CVSS 3.1 · Published 2023-12-12

Uptime Kuma is an open-source monitoring platform that tracks the uptime and status of services and websites. This vulnerability allows previously logged-in users to maintain full read-write access to the platform even after the account password is changed, as long as they don't explicitly log out. An attacker with temporary access to a user's device could gain permanent unauthorized access to the monitoring system and sensitive operational data.

Technologies: uptime-kuma (npm). Vendors: npm.

Quick answers

Is CVE-2023-49804 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2023-49804 being exploited in the wild.
How severe is CVE-2023-49804?: Low severity, with a CVSS score of 3.1, published 12 December 2023.
Which products and versions are affected?: uptime-kuma (npm) SEMVER:introduced=0,fixed=1.23.9.
Is there a fix for CVE-2023-49804?: Yes. uptime-kuma (npm): upgrade to 1.23.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2023-49804 attacked?: It is attacked with local access or from the adjacent network, in a web application.
Am I affected by CVE-2023-49804?: Check whether you run uptime-kuma (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

uptime-kuma (npm): upgrade to 1.23.9 or later
```
npm install uptime-kuma@1.23.9
```

Technical details

The vulnerability is a session management flaw (CWE-384: Session Fixation) in Uptime Kuma's authentication system. When a user changes their password, the platform fails to invalidate all existing authenticated socket connections and JWT tokens for that user. This allows previously authenticated clients to retain full access without re-authentication, even across system restarts and browser cache clears. The attack requires local or adjacent access to a device where the user was previously authenticated, or compromised credentials on an existing session. The fix, released in version 1.23.9, makes the server emit a refresh event and disconnect all clients except the one initiating the password change.

Affected products

Louis Lam Uptime Kuma before 1.23.9

Identifiers

CVE-2023-49804
GHSA-88j4-pcx8-q4q3

Timeline

2023-12-07: disclosed: Vulnerability reported in public issue tracker (against security policy)
2023-12-10: patched: Uptime Kuma released patch version 1.23.9
2023-12-10: advisory: GHSA-88j4-pcx8-q4q3 and CVE-2023-49804 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.