CasaOS Username Enumeration - Bypass of CVE-2024-24766GHSA-hcw2-2r9c-gc6p
MEDIUMFix: IceWhaleTech/CasaOS-UserService@dd927feGHSA-hcw2-2r9c-gc6p is a medium-severity (CVSS 6.2) CWE-204 vulnerability in github.com/IceWhaleTech/CasaOS-UserService. A fix is available for github.com/IceWhaleTech/CasaOS-UserService — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-hcw2-2r9c-gc6p.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/IceWhaleTech/CasaOS-UserServiceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The Casa OS Login page has disclosed the username enumeration vulnerability in the login page which was patched in CasaOS v0.4.7.
Details
It is observed that the attacker can enumerate the CasaOS username using the application response. If the username is incorrect the application gives the error "User does not exist" with success code "10006", If the password is incorrect the application gives the error "User does not exist or password is invalid" with success code "10013".
PoC
- If the Username is invalid application gives "User does not exist" with success code "10006".
- If the Password is invalid application gives "User does not exist or password is invalid" with success code "10013".
Impact
Using this error attacker can enumerate the username of CasaOS.
The logic behind the issue
The logic behind the issue If the username is incorrect, then throw an error "User does not exist" with success code "10006", else throw an error "User does not exist or password is invalid" with success code "10013".
This condition can be vice versa like:
If the password is incorrect, then throw an error "User does not exist or password is invalid" with success code "10013", else throw an error "User does not exist" with success code "10006".
Mitigation
Since this is the condition we have to implement a single error which can be "Username/Password is Incorrect!!!" with single success code.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/IceWhaleTech/CasaOS-UserService | ≥ 0.4.7&&< 0.4.8 | 0.4.8go get github.com/IceWhaleTech/CasaOS-UserService@v0.4.8 |
Affected Products
casaos-userserviceicewhaleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/IceWhaleTech/CasaOS-UserService, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/IceWhaleTech/CasaOS-UserService to 0.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hcw2-2r9c-gc6p 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.
Frequently Asked Questions
Is GHSA-hcw2-2r9c-gc6p in your dependencies?
Find it across Go, including transitive dependencies.