How severe is GHSA-23q2-5gf8-gjpp?

No CVSS score has been assigned to GHSA-23q2-5gf8-gjpp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-23q2-5gf8-gjpp?

GHSA-23q2-5gf8-gjpp affects the following packages: uptime-kuma (npm). Ecosystems affected: npm.

How do I fix GHSA-23q2-5gf8-gjpp?

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.

How do I detect GHSA-23q2-5gf8-gjpp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-23q2-5gf8-gjpp if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-23q2-5gf8-gjpp?

O3 pinpoints whether GHSA-23q2-5gf8-gjpp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-23q2-5gf8-gjpp actively exploited in the wild?

No public exploit code has been indexed for GHSA-23q2-5gf8-gjpp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-23q2-5gf8-gjpp published, and has it been updated?

GHSA-23q2-5gf8-gjpp was published on April 19, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-23q2-5gf8-gjpp

Enabling Authentication does not close all logged in socket connections immediately

Published

Apr 19, 2024

Updated

Apr 19, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

uptime-kumanpm

53downloads / 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`uptime-kuma`	all versions	1.23.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uptime-kuma. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
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.
How O3 protects you
O3 pinpoints whether GHSA-23q2-5gf8-gjpp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-23q2-5gf8-gjpp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-23q2-5gf8-gjpp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works