Account takeover via indefinitely valid session tokens
Published Oct 9, 2023 · Updated Sep 18, 2024
Session-token validation failure in Louis Lam Uptime Kuma before 1.23.3 allows local users to retain account access with a copied JWT. The server accepts previously issued JWTs indefinitely because authentication checks neither password changes nor inactivity; the patch binds each token to a password hash. Exploitation requires access to a user's device and token, after which monitors, notification secrets, settings, and stored history can be read or altered.
Summary
What happened
Session-token validation failure in Louis Lam Uptime Kuma before 1.23.3 allows local users to retain account access with a copied JWT. The server accepts previously issued JWTs indefinitely because authentication checks neither password changes nor inactivity; the patch binds each token to a password hash. Exploitation requires access to a user's device and token, after which monitors, notification secrets, settings, and stored history can be read or altered.
The record
- CVE
- CVE-2023-44400
- Published
- Oct 9, 2023
- Updated
- Sep 18, 2024
- Vendor
- Louis Lam
- Product
- Uptime Kuma
- Classifications
- CWE-384, T1550.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 9, 2023CVE publishedPublication date reported by the CVE source.
- Sep 18, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.23.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Password-change and inactivity token-reuse proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo