NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

Enabling Authentication does not close all logged in socket connections immediatelyGHSA-23q2-5gf8-gjpp

Fix: louislam/uptime-kuma@7a9e2f5

GHSA-23q2-5gf8-gjpp is a security vulnerability in uptime-kuma. A fix is available for uptime-kuma — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Apr 19, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
uptime-kumanpm
105downloads / week

Description

Summary

This is basically GHSA-88j4-pcx8-q4q but instead of changing passwords, when enabling authentication.

PoC

  • Open Uptime Kuma with authentication disabled
  • Enable authentication using another window
  • Access the platform using the previously logged-in window
  • Note that access (read-write) remains despite the enabled authentication
  • Expected behaviour:
    • After enabling authentication, all previously connected sessions should be invalidated, requiring users to log in.
  • Actual behaviour:
    • The system retains sessions and never logs out users unless explicitly done by clicking logout or refreshing the page.

Impact

See GHSA-g9v2-wqcj-j99g and GHSA-88j4-pcx8-q4q

TBH this is quite a niche edge case, so I don't know if this even warrants a security report.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmuptime-kumaall versions1.23.12npm install uptime-kuma@1.23.12

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update uptime-kuma to 1.23.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23q2-5gf8-gjpp is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Summary This 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. ### PoC - Open Uptime Kuma with authentication disabled - Enable authentication using another window - Access the platform using the previously logged-in window - Note that access (read-write) remains despite the enabled authentication - Expected behaviour: - After enabling authentication, all previously connected sessions should be invalidated, requiring users to log in. - Actual behaviour: - T
O3 Security · Impact-Aware SCA

Is GHSA-23q2-5gf8-gjpp in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Enabling Authentication does not close all logged in…