Advisory

GHSA-23q2-5gf8-gjpp

Also known as: None

Summary

Enabling Authentication does not close all logged in socket connections immediately

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2024-04-19 17:26 UTC
Modified
2024-04-19 17:26 UTC

Affected packages and fixes

uptime-kuma

npm · All systems

Affected

  • introduced 0, fixed 1.23.12 (semver)

Fixed versions

1.23.12

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences