CVE-2024-6832: CWE-693: Protection Mechanism Failure in WSO2 WSO2 Enterprise Integrator
The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores. When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.
AI Analysis
Technical Summary
The vulnerability arises because the account locking mechanism in WSO2 Enterprise Integrator 6.6.0 does not maintain a consistent state when it cannot reach all configured user stores, particularly secondary ones. As a result, the lockout mechanism is bypassed for users in accessible stores, enabling attackers to perform unlimited invalid authentication attempts without triggering account lockout. This is classified under CWE-693 (Protection Mechanism Failure).
Potential Impact
Users in accessible user stores are vulnerable to brute force attacks due to the failure of the account lockout mechanism when secondary user stores are unreachable. This can lead to unauthorized access if attackers successfully guess passwords. The CVSS score is 5.9 (medium severity), indicating a moderate impact primarily on confidentiality.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, organizations should monitor authentication attempts and consider additional protective controls such as multi-factor authentication or limiting access to user stores to reduce risk.
CVE-2024-6832: CWE-693: Protection Mechanism Failure in WSO2 WSO2 Enterprise Integrator
Description
The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores. When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.
CVSS v3.1
Score 5.9medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because the account locking mechanism in WSO2 Enterprise Integrator 6.6.0 does not maintain a consistent state when it cannot reach all configured user stores, particularly secondary ones. As a result, the lockout mechanism is bypassed for users in accessible stores, enabling attackers to perform unlimited invalid authentication attempts without triggering account lockout. This is classified under CWE-693 (Protection Mechanism Failure).
Potential Impact
Users in accessible user stores are vulnerable to brute force attacks due to the failure of the account lockout mechanism when secondary user stores are unreachable. This can lead to unauthorized access if attackers successfully guess passwords. The CVSS score is 5.9 (medium severity), indicating a moderate impact primarily on confidentiality.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, organizations should monitor authentication attempts and consider additional protective controls such as multi-factor authentication or limiting access to user stores to reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- WSO2
- Date Reserved
- 2024-07-17T11:44:02.821Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7441c2bf8831d53967eba6
Added to database: 08/06/2026, 08:11:46 UTC
Last enriched: 08/06/2026, 08:30:03 UTC
Last updated: 08/07/2026, 02:11:36 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.