Headline
GHSA-c967-2652-gfjm: CasaOS Username Enumeration
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!!!”
Package
gomod github.com/IceWhaleTech/CasaOS-UserService (Go)
Affected versions
>= 0.4.4.3, < 0.4.7
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!!!”
References
- GHSA-c967-2652-gfjm
- IceWhaleTech/CasaOS-UserService@c75063d
- https://github.com/IceWhaleTech/CasaOS-UserService/releases/tag/v0.4.7
Published to the GitHub Advisory Database
Mar 6, 2024