Skip to content

CasaOS Username Enumeration - Bypass of CVE-2024-24766

Moderate severity GitHub Reviewed Published Apr 1, 2024 in IceWhaleTech/CasaOS-UserService • Updated Apr 3, 2024

Package

gomod github.com/IceWhaleTech/CasaOS-UserService (Go)

Affected versions

= 0.4.7

Patched versions

0.4.8

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

  1. If the Username is invalid application gives "User does not exist" with success code "10006".

1

  1. If the Password is invalid application gives "User does not exist or password is invalid" with success code "10013".

2

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.

References

Published to the GitHub Advisory Database Apr 1, 2024
Reviewed Apr 1, 2024
Published by the National Vulnerability Database Apr 1, 2024
Last updated Apr 3, 2024

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

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-28232

GHSA ID

GHSA-hcw2-2r9c-gc6p

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.