Increased password guessing via identifier-specific regulation keys
Published Feb 19, 2025 · Updated Feb 19, 2025
Improper login-attempt restriction in Authelia before 4.38.19 allows remote authenticated users to double password guesses. The first-factor handler keyed regulation checks and attempt records by the submitted username or email instead of resolving both forms to the account username. Exploitation requires email login, weak passwords, and reduced regulation protection; default bans and multifactor authentication substantially limit account compromise.
Summary
What happened
Improper login-attempt restriction in Authelia before 4.38.19 allows remote authenticated users to double password guesses. The first-factor handler keyed regulation checks and attempt records by the submitted username or email instead of resolving both forms to the account username. Exploitation requires email login, weak passwords, and reduced regulation protection; default bans and multifactor authentication substantially limit account compromise.
The record
- CVE
- CVE-2025-24806
- Published
- Feb 19, 2025
- Updated
- Feb 19, 2025
- Vendor
- Authelia
- Product
- Authelia
- Classifications
- CWE-307, T1110.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.38.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo