Advisory

GHSA-hcw2-2r9c-gc6p

Also known as: CVE-2024-28232, GO-2024-2668

Summary

CasaOS Username Enumeration - Bypass of CVE-2024-24766

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-04-01 15:48 UTC
Modified
2026-02-04 03:47 UTC

Affected packages and fixes

github.com/IceWhaleTech/CasaOS-UserService

Go · All systems

Affected

  • introduced 0.4.7, fixed 0.4.8 (semver)

Fixed versions

0.4.8

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences