CasaOS Username Enumeration - Bypass of CVE-2024-24766

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-28232: 0.62% estimated exploitation activity in the next 30 days; percentile 49.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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". 2. If the Password is invalid application gives "User does not exist or password is invalid" with success code "10013". 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"…

Published by the source

1 Apr 2024, 15:48 UTC

Last modified by the source

3 Apr 2024, 18:59 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hcw2-2r9c-gc6p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-28232

Advisory: CasaOS Username Enumeration - Bypass of CVE-2024-24766
IDs: CVE-2024-28232, GHSA-hcw2-2r9c-gc6p
Record: https://patchnext.com/advisories/cve-2024-28232 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/IceWhaleTech/CasaOS-UserService 0.4.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/IceWhaleTech/CasaOS-UserService: affected >= 0.4.7, <= 0.4.7; fixed in 0.4.8

## Suggested inspection (read-only)
- Go github.com/IceWhaleTech/CasaOS-UserService: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/IceWhaleTech/CasaOS-UserService.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hcw2-2r9c-gc6p (GitHub-reviewed advisory GHSA-hcw2-2r9c-gc6p lists affected ranges: Go github.com/IceWhaleTech/CasaOS-UserService >=0.4.7 <=0.4.7)

Commands are suggestions: review each one before running it.