CVE-2025-9824
Last modified
CVE-2025-9824 is a medium-severity vulnerability rated 5.9/10 on the CVSS scale. ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks. PatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not. Technical DetailsThe vulnerability was caused by different response times when: * A valid username was provided (password hashing occurred) * An invalid username was provided (no password hashing occurred) The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing. WorkaroundsNo workarounds are available. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
Description
ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks. PatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not. Technical DetailsThe vulnerability was caused by different response times when: * A valid username was provided (password hashing occurred) * An invalid username was provided (no password hashing occurred) The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing. WorkaroundsNo workarounds are available. Users should upgrade to the patched version. References * https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-9824?
How severe is CVE-2025-9824?
How do I fix CVE-2025-9824?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-9817SSH dissector crash in Wireshark 4.4.0 to 4.4.8 allows denia…7.5
- CVE-2025-9818A vulnerability (CWE-428) has been identified in the Uninter…6.7
- CVE-2025-9820A flaw was found in the GnuTLS library, specifically in the …4
- CVE-2025-9821SummaryUsers with webhook permissions can conduct SSRF via w…2.7
- CVE-2025-9822SummaryA user with administrator rights can change the confi…5.5
- CVE-2025-9823SummaryA Cross-Site Scripting (XSS) vulnerability allows an …4.8
- CVE-2025-9825GitLab has remediated an issue in GitLab CE/EE affecting all…6.5
- CVE-2025-9826Stored cross-site scripting vulnerability in M-Files Hubshar…5.4
- CVE-2025-9828A vulnerability was determined in Tenda CP6 11.10.00.243. Th…5.9
- CVE-2025-9829A vulnerability was identified in PHPGurukul Beauty Parlour …9.8
- CVE-2025-9830A security flaw has been discovered in PHPGurukul Beauty Par…9.8
- CVE-2025-9831A weakness has been identified in PHPGurukul Beauty Parlour …9.8
Are you affected by CVE-2025-9824?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
