Skip to content

Username Enumeration in CasaOS

Moderate
tigerinus published GHSA-c967-2652-gfjm Mar 6, 2024

Package

https://github.com/IceWhaleTech/CasaOS-UserService (Casa OS)

Affected versions

v0.4.4.3

Patched versions

v0.4.7

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!!!"

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE ID

CVE-2024-24766

Weaknesses

Credits