CVE-2024-24766 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.
CasaOS Username Enumeration
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 CVE-2024-24766.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-24766 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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.
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!!!"
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/IceWhaleTech/CasaOS-UserService | ≥ 0.4.4.3&&< 0.4.7 | 0.4.7go get github.com/IceWhaleTech/CasaOS-UserService@v0.4.7 |
Detection & 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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-24766 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-24766 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-24766. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-24766 in your dependencies?
O3 Security finds CVE-2024-24766 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.