Account lockout denial of service via username targeting
Published Sep 5, 2024 · Updated Sep 5, 2024
Improper login throttling in RapidIdentity LTS through 2023.0.2 and Cloud through 2024.08.0 allows remote attackers to lock accounts. The /api/rest/authn flow accepts a target username and globally locks that account after repeated invalid password submissions instead of limiting attempts by requester. Exploitation requires knowledge of a valid username; recurring submissions prolong the lockout and deny that user access without exposing or altering account data.
Summary
What happened
Improper login throttling in RapidIdentity LTS through 2023.0.2 and Cloud through 2024.08.0 allows remote attackers to lock accounts. The /api/rest/authn flow accepts a target username and globally locks that account after repeated invalid password submissions instead of limiting attempts by requester. Exploitation requires knowledge of a valid username; recurring submissions prolong the lockout and deny that user access without exposing or altering account data.
The record
- CVE
- CVE-2024-45589
- Published
- Sep 5, 2024
- Updated
- Sep 5, 2024
- Vendor
- Identity Automation
- Product
- RapidIdentity Cloud
- Classifications
- CWE-307, T1531
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2024CVE publishedPublication date reported by the CVE source.
- Sep 5, 2024Record 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=0 <=2024.08.0
What conditions does exploitation require?
What is affected?
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
- RidLocker authentication lockout proof of conceptproof of concept · demonstrated
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