NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

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

low

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…

Published Apr 19, 2024

Affected packages

uptime-kuma

Ecosystem
npm
Affected
<= 1.23.11
Fixed in
1.23.12
Check
npm ls uptime-kuma

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries