github.com/authelia/authelia/v4
Affected
- introduced
0, fixed4.38.19(semver)
Fixed versions
4.38.19
Fix
- Fixed version
4.38.19go get github.com/authelia/authelia/[email protected]
Advisory
Also known as: CVE-2025-24806, GO-2025-3468
Authelia applies regulation separately to Username-based logins to Email-based logins
Summary
If users are allowed to sign in via both username and email the regulation system treats these as separate login events. This leads to the regulation limitations being effectively doubled assuming an attacker using brute-force to find a user password. It's important to note that due to the effective operation of regulation where no user-facing sign of their regulation ban being visible either via timing or via API responses, it's effectively impossible to determine if a failure occurs due to a bad username password combination, or a effective ban blocking the attempt which heavily mitigates any form of brute-force.
Details
This occurs because the records and counting process for this system uses the method utilized for sign in rather than the effective username attribute.
Impact
This has a minimal impact on account security, this impact is increased naturally in scenarios when there is no two-factor authentication required and weak passwords are used. This makes it a bit easier to brute-force a password.
Workarounds
Low Basis: The source's own band: LOW
0, fixed 4.38.19 (semver)4.38.19
4.38.19go get github.com/authelia/authelia/[email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0