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.
Blast Radius
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.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-c967-2652-gfjm 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 pinpoints whether GHSA-c967-2652-gfjm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-c967-2652-gfjm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-c967-2652-gfjm in your dependencies?
O3 detects GHSA-c967-2652-gfjm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.