Skip to content

Enabling Authentication does not close all logged in socket connections immediately

Low
louislam published GHSA-23q2-5gf8-gjpp Apr 19, 2024

Package

docker louislam/uptime-kuma (Docker)

Affected versions

<=1.23.11

Patched versions

1.23.12
npm louislam/uptime-kuma (npm)
<=1.23.11
1.23.12

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.

Severity

Low

CVE ID

No known CVE

Weaknesses

No CWEs