Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

CasaOS Username Enumeration

Historical advisory saved 24 Oct 2026 13:19:41 UTC. The publisher may have updated it since then. Latest advisory.

osv · GHSA-c967-2652-gfjm

Published

### Summary The Casa OS Login page has disclosed the username enumeration vulnerability in the login page. ### Details It is observed that the attacker can enumerate the CasaOS username using the application response. If the username is incorrect application gives the error "**User does not exist**", If the password is incorrect application gives the error "**Invalid password**". ### PoC Capture the login request in a tool like Burp Suit and use the intruder tab for trying multiple usernames. Keep checking the response of each request if the response says **Invalid password** then the username is right. ### Impact Using this error attacker can enumerate the username of CasaOS. ### The logic behind the issue If the username is incorrect, then throw an error "User does not exist" else throw an error "Invalid password". This condition can be vice versa like: If the password is incorrect, then throw an error "Invalid password" else throw an error "User does not exist". ### Mitigation Since this is the condition we have to implement a single error which can be "Username/Password is Incorrect!!!"

Source published
6 Mar 2024 15:23:53 UTC
Source modified
10 Sep 2026 03:50:10 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 02:42 UTC · 273 of 275 readable · 270 fully read · documentation 469/469 current